Check if an email, domain, or URL appears in known data breaches or
AI agents call breach_exposure_check to retrieve information from MCP OSINT Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs passive reconnaissance by querying breach databases, which is characteristic of Read category tools. Severity is medium rather than low because breach data exposure checks can reveal sensitive information about individuals or organizations (PII, credentials, compromised accounts), which could be misused by an agent to target individuals or guide further attacks, though the tool itself performs no…
From the tool's definition Checks if an email, domain, or URL appears in known data breaches. This is a query/lookup operation against breach databases with no side effects—it retrieves information without modifying, deleting, or executing external actions.
Attacks that exploit this kind of access
Check if an email, domain, or URL appears in known data breaches or. It is categorised as a Read tool in the MCP OSINT Server MCP Server, which means it retrieves data without modifying state.
Register the MCP OSINT Server MCP server in PolicyLayer and add a rule for breach_exposure_check: 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 MCP OSINT Server. Nothing to install.
breach_exposure_check 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 breach_exposure_check 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 breach_exposure_check. 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.
breach_exposure_check is provided by the MCP OSINT Server MCP server (lliwi/osint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →