aidefence_has_pii
Check if input contains PII (emails, SSNs, API keys, passwords, etc.). Use when nothing native exists — Claude Code does not have a PII / prompt-injection / adversarial-text scanner. Pair with any tool that ingests untrusted input (browser scrape, federation envelope, memory_import_claude).
This record as markdown: /tools/hamza-agent-hub-252/aidefence-has-pii.md
What aidefence_has_pii does on Hamza Agent Hub 252
AI agents call aidefence_has_pii to retrieve information from Hamza Agent Hub 252 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why aidefence_has_pii is rated Low
This is a detection/analysis tool that examines data and reports findings. It retrieves information (whether PII is present) without creating, modifying, deleting, or executing anything. The low severity reflects minimal blast radius: a false negative could allow PII to pass through, but the tool itself cannot move money, delete data, or execute code. It is purely informational.
From the tool's definition Tool checks/scans input for PII patterns and returns detection results. Description states 'Check if input contains PII' — a query operation with no side effects, data modification, or external state changes.
Attacks that exploit this kind of access
The rule that runs aidefence_has_pii safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hamza Agent Hub 252, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For aidefence_has_pii, this is the rule to start with:
aidefence_has_pii is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hamza Agent Hub 252, apply this rule, and every aidefence_has_pii call is checked against it from then on.
Questions about aidefence_has_pii
Check if input contains PII (emails, SSNs, API keys, passwords, etc.). Use when nothing native exists — Claude Code does not have a PII / prompt-injection / adversarial-text scanner. Pair with any tool that ingests untrusted input (browser scrape, federation envelope, memory_import_claude). It is categorised as a Read tool in the Hamza Agent Hub 252 MCP Server, which means it retrieves data without modifying state.
Register the Hamza Agent Hub 252 MCP server in PolicyLayer and add a rule for aidefence_has_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 Hamza Agent Hub 252. Nothing to install.
aidefence_has_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 aidefence_has_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 aidefence_has_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.
aidefence_has_pii is provided by the Hamza Agent Hub 252 MCP server (hamzachallenge3-dev/hamza-agent-hub-252). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hamza Agent Hub 252, and thousands of servers like it.
This server
Across the catalogue