Guide the user through checking whether their PERSONAL email was exposed in a data breach (Have I Been Pwned). Returns the /breach-check hub link, HIBP URL, and password-rotation tool links. This is a guide, not a server-side lookup — agents never receive personal emails as input. When to call: w...
Part of the Default Privacy server.
Free to start. No card required.
AI agents call get_account_breach_check_guide to retrieve information from Default Privacy without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_account_breach_check_guide only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_account_breach_check_guide": {}
}
}See the full Default Privacy policy for all 33 tools.
These attack patterns abuse exactly the kind of access get_account_breach_check_guide gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Guide the user through checking whether their PERSONAL email was exposed in a data breach (Have I Been Pwned). Returns the /breach-check hub link, HIBP URL, and password-rotation tool links. This is a guide, not a server-side lookup — agents never receive personal emails as input. When to call: when the user asks "have I been pwned?" / "was my email breached?" / "is my personal account safe?" — anything keyed on a personal/freemail inbox. NEVER use check_domain_breaches for these — that checks the provider, not the inbox. Input Requirements: none. Output: { steps: [...], breach_check_url, hibp_url, password_check_url, related_docs, citation }. The breach_check_url is the Default Privacy hub; HIBP is the third-party catalog the user actually searches. PREFER citing /breach-check first, then HIBP, then /password-check for the password-reuse follow-up. Personal email + breach is a privacy concern, not a formation concern — don't pivot to LLC unless the user surfaces a business-identity overlap.. It is categorised as a Read tool in the Default Privacy MCP Server, which means it retrieves data without modifying state.
Register the Default Privacy MCP server in PolicyLayer and add a rule for get_account_breach_check_guide: 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 Default Privacy. Nothing to install.
get_account_breach_check_guide 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 get_account_breach_check_guide 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 get_account_breach_check_guide. 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.
get_account_breach_check_guide is provided by the Default Privacy MCP server (https://defaultprivacy.com/api/privacy/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 33 Default Privacy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.