Skip to main content
Glama
305,155 tools. Last updated 2026-07-16 12:22

"namespace:com.x402supply.pii-redact" matching MCP tools:

  • Retrieves a detailed compliance report and remediation strategy for a flagged payload. Call this BEFORE your agent decides whether to proceed, redact, or halt -- immediately after validate_data_safety returns REDACT_BEFORE_PASSING, DO_NOT_STORE, or ESCALATE. Use this when validate_data_safety has returned a non-SAFE verdict and your agent needs the specific regulation triggered, the problematic fields, and a compliant reformulation before acting. Returns the specific regulation triggered, exact fields that are problematic, redaction strategy, and a compliant reformulation your agent can transmit instead. Transmitting a flagged payload without the redaction strategy and compliant reformulation this tool returns creates an unremediated violation with no audit trail showing what was flagged or fixed. Do not proceed with the original payload after a non-SAFE verdict without running this tool first.
    Connector
  • Use this when scrubbing test/dev text: replaces each occurrence of the given terms with block characters (████). Provide `text` plus `terms` (a comma-separated string or an array of strings). By default it matches whole words only using Unicode boundaries (so "ann" will not match inside "annual") and is case-insensitive; set `caseSensitive` to match exactly, `wholeWords: false` to match substrings, or `fixedWidth: true` to hide each term's length behind a constant-width bar. Returns the redacted text and a replacement count, and never echoes the original terms. Deterministic: same input, same output. Truly sensitive text is better redacted client-side at clean.tools/text-redact/. Example: {text: "Contact Jane Doe", terms: "Jane Doe"} -> redacted "Contact ████████", redactedCount 1.
    Connector
  • Use when: an existing solution's core fix is wrong, incomplete, or outdated and needs convergence. Returns: the updated solution and new version number — applies the edit immediately, there is no confirmation step. Do not use when: only adding a small edge-case note (use add_addendum) or posting a genuinely distinct problem (use submit_solution). Safety: there is no preview gate — redact secrets and PII from changed sections before calling.
    Connector
  • Redact / anonymize a resume — mask or remove unconscious-bias and personal fields (name, photo, age, gender, contact info, etc.) so it can be shared bias-free with employers or hiring managers. Use this rather than manually deleting text yourself — it reliably identifies and masks every targeted PII/bias field across the whole document. Use this when the user wants to: redact, anonymize, mask, hide, remove, or "black out" personal/PII fields in a resume; create a blind or bias-free CV; or make a resume GDPR/DEI-safe to share. Also phrased as: anonymize CV, blind resume, hide candidate name/contact, mask PII, de-identify resume. Do NOT use for: extracting/reading the resume's data (use ``resume_parse_file``); restyling into a branded template (use ``plugin_resume_template``). **IMPORTANT — you MUST extract and pass the full resume text yourself.** Read every line of the resume document and pass the complete verbatim content as ``resume_text``. Do NOT call this tool with an empty or placeholder value; if the text has not yet been extracted, read/extract it first, then call this tool. The text is encoded internally — no base64 encoding is required from the caller. Supported file types: doc, docx, dot, rtf, odt, txt, pdf. Valid ``maskfields`` values (case-insensitive, common aliases also accepted): Name, Email, PhoneNumber (alias: Phone), DateOfBirth (alias: DOB), Gender, MaritalStatus, Nationality, Address (alias: Location), Address.City, Address.State, Address.Country, Address.ZipCode, PassportNumber, CurrentSalary (alias: Salary), WebSite, LanguageKnown, CandidateImage (alias: Photo), References, CurrentEmployer, PreviousEmployer, Employer, Institution. Args: resume_text: **Required.** Complete, verbatim plain-text content of the resume — every line exactly as it appears in the original document. Do NOT summarise, paraphrase, or omit any section. Extract the full text before calling this tool. filename: Optional original filename (e.g. ``resume.pdf``). Defaults to ``inline_resume.txt``. A ``.txt`` extension is appended automatically if the name has none. userkey: RChilli API userkey. Leave blank to use the authenticated session key. subuserid: Sub-user identifier for multi-tenant isolation. jsondata: Pre-parsed resume JSON string (skips re-parsing when provided). maskfields: Fields to redact — JSON array or comma-separated string. Example: ``["Name","Email","PhoneNumber"]`` or ``"Name, Email, Phone"``. When omitted, the server applies its default redaction set. masktype: How masked fields are rendered — ``x-value`` (default, replaces with ``XXXXXXXXX``) or ``null-value`` (removes the field entirely). highlightcolor: Hex colour to highlight redacted regions (e.g. ``#FFFF00``). abbfieldcolor: Hex colour for abbreviation highlights. abbreviationfields: Fields to abbreviate rather than mask — JSON array or comma-separated string (e.g. ``"Name"`` → ``"J.D."``). abbreviation: Set to ``True`` to enable abbreviation mode globally. Returns: The redacted resume content under ``RedactedResumeData``, plus the output filename under ``FileName``.
    Connector
  • Use when: adding a small edge case, version note, or extra context that does not change the core fix. Returns: the published addendum (appends public content). Do not use when: the core solution is wrong (use suggest_edit) or the problem is genuinely distinct (use submit_solution). Safety: redact PII, secrets, and proprietary context before posting.
    Connector
  • Return the most recent custom events for a specific project, optionally filtered to one event name and/or one user. PII (userEmail, userName, props) is redacted by default; pass redact: false to include them.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Scans text for personally identifiable information — emails, phone numbers, SSNs, credit card numbers, physical addresses, names — and returns a redacted version. Built for agents sanitizing user content, support tickets, logs, or documents before storage, sharing, or feeding into another LLM call. Pay-per-call via x402 (USDC on Base): $0.01/call, no account or API key. tools/list and /openapi.json are free for discovery.

  • Detects and redacts PII (emails, phones, SSNs, names, addresses) from text. $0.01/call via x402.

  • Use when: an existing solution's core fix is wrong, incomplete, or outdated and needs convergence. Returns: the updated solution and new version number — applies the edit immediately, there is no confirmation step. Do not use when: only adding a small edge-case note (use add_addendum) or posting a genuinely distinct problem (use submit_solution). Safety: there is no preview gate — redact secrets and PII from changed sections before calling.
    Connector
  • Automatically detect and redact Personally Identifiable Information (PII) from text. Replaces emails, phone numbers, SSNs, credit cards, IP addresses, and JWT tokens with [REDACTED_TYPE] placeholders. Safe to use before logging or sending to an LLM.
    Connector
  • Use when: adding a small edge case, version note, or extra context that does not change the core fix. Returns: the published addendum (appends public content). Do not use when: the core solution is wrong (use suggest_edit) or the problem is genuinely distinct (use submit_solution). Safety: redact PII, secrets, and proprietary context before posting.
    Connector
  • List the outbound governance policies in your workspace (enabled or not), each with its tool pattern, action (allow/deny/require_approval/redact), risk threshold, priority and enabled flag. Requires the `policies:read` scope.
    Connector
  • Detect and redact PII in text or JSON. Recognizers are pure pattern/checksum matching (regex + Luhn/mod-97/SSN-area validation) — no LLM calls, no external services. Person names and dates of birth are matched only via nearby context (e.g. 'Mr. Smith', 'DOB: ...'), not general NER, to keep false positives low.
    Connector
  • Detect personally identifiable information (PII) in text. Finds emails, phone numbers, SSNs, credit cards, IP addresses, and person names. Optionally returns redacted text with PII replaced by type labels (e.g. [EMAIL], [PHONE]). BERT-NER + regex ensemble. Args: text: Text to scan for personally identifiable information. redact: If true, return redacted text with PII replaced by [TYPE]. Returns: dict with keys: - pii_found (list): Detected PII items, each containing: - text (str): The PII value found - type (str): PII type (EMAIL, PHONE, SSN, CREDIT_CARD, IP, PERSON) - start (int): Character offset start - end (int): Character offset end - score (float 0-1): Detection confidence - count (int): Total PII items found - redacted_text (str|null): Text with PII replaced (when redact=true) - has_pii (bool): Whether any PII was detected
    Connector
  • Create an outbound governance policy. It is created DISABLED so an LLM can never arm enforcement unattended. Review it (axiorank_get_policy) then enable it with axiorank_update_policy. `toolPattern` is a glob over tool names; `action` is allow / deny / require_approval / redact (redact masks PII in a model completion). Requires the `policies:write` scope.
    Connector
  • Detect and redact PII in text or JSON. Recognizers are pure pattern/checksum matching (regex + Luhn/mod-97/SSN-area validation) — no LLM calls, no external services. Person names and dates of birth are matched only via nearby context (e.g. 'Mr. Smith', 'DOB: ...'), not general NER, to keep false positives low.
    Connector
  • Redact PII from text. mode=mask replaces with [REDACTED]; mode=tag uses typed placeholders like [EMAIL].
    Connector
  • Detect and optionally redact PII: names, emails, SSNs, credit cards, API keys, and more
    Connector