Skip to main content
Glama
privacyscrubber-mcp

privacyscrubber-mcp

Audit Text for PII & Secret Exposure (ZTDS RFC v1.0)

ztds_audit
Read-onlyIdempotent

Audits text in RAM for cleartext PII and secret exposure, returning risk level, entity breakdown, SHA-256 hash, and RFC v1.0 compliance flags without persisting session state.

Instructions

Drop-in ZTDS RFC v1.0 read-only dry-run audit. Inspects text in RAM and returns riskLevel (CLEAN/MODERATE/CRITICAL), entity breakdown, SHA-256 contentHash, and RFC v1.0 compliance flags without persisting session state.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "ztds_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesUTF-8 text, prompt, or configuration snippet to inspect for cleartext PII and secret exposure.
sectorNoOptional alias for 'profile'. The industry sector or compliance vertical to apply (e.g. 'medical', 'finance', 'legal', 'dev', 'hr', 'accounting', 'security', 'compliance', 'underwriting', 'telecom').
profileNoThe detection profile to use. Available: 'General' (Free, 15,000 chars), or 30 specialized industry profiles (5,000 chars Free trial quota; unlimited on PRO/TEAMS/SDK): 'Dev' (Engineering/Code), 'Medical', 'Pharma', 'Biotech', 'Telecom', 'Legal', 'Compliance', 'CCPA', 'Finance', 'Bizops', 'Sales', 'WealthMgmt', 'Insurance', 'Accounting', 'Underwriting', 'Automotive', 'Energy', 'Hospitality', 'HR', 'Security', 'Marketing', 'Support', 'RealEstate', 'Agents', 'Academic', 'Creative', 'Tech', 'Personal', 'Engineering'. Defaults to 'General'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.5.1

TDQS

A3.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds valuable context beyond that: it is a dry-run audit, inspects in RAM, does not persist session state, and returns riskLevel, entity breakdown, SHA-256 contentHash, and compliance flags. Quota/limit details are left to the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two compact sentences and front-loads the core operation. 'Drop-in ZTDS RFC v1.0' is jargon-heavy but efficiently establishes the contract, and there is no filler content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-text audit tool with fully documented parameters and clear annotations, the description covers purpose, non-persistence, and output fields. The only notable gap is sibling routing guidance, which is minor relative to the schema and annotation richness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the schema already documents text, sector, and profile in detail, including available profiles and character limits. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific action: inspect text in RAM for cleartext PII and secret exposure. The phrase 'text in RAM' implicitly distinguishes it from directory/file audit siblings, but it does not explicitly name or differentiate from alternatives such as audit_directory_for_pii.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no explicit when-to-use, when-not-to-use, or routing guidance versus siblings like audit_directory_for_pii, sanitize_text, or reveal_text. Usage is implied by 'Inspects text,' but an agent gets no exclusion guidance or alternative selection criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.