Detect PII in content without redacting Use when native package install (
AI agents call transfer_detect-pii to retrieve information from Claude Flow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes data to identify personally identifiable information, matching the Read category (queries/analyzes data with no side effects). Severity is low because detection itself causes no harm—it only exposes what PII exists. The lack of redaction confirms non-destructive analysis.
From the tool's definition Tool name contains 'detect' and description states 'Detect PII in content without redacting'. The core function is detection/analysis, which is a read operation that scans content to identify sensitive information but performs no modification, deletion, or…
Attacks that exploit this kind of access
Detect PII in content without redacting Use when native package install (. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.
Register the Claude Flow MCP server in PolicyLayer and add a rule for transfer_detect-pii: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Claude Flow. Nothing to install.
transfer_detect-pii is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the transfer_detect-pii rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for transfer_detect-pii. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
transfer_detect-pii is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.