hibp_check_account
Check if an email account has been in a data breach.
This record as markdown: /tools/creativelead-unclick/hibp-check-account.md
What hibp_check_account does on UnClick
AI agents call hibp_check_account to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | — | |
api_key | string | — |
Parameters from the server's own tool schema.
Why hibp_check_account is rated Low
The tool performs a read-only query against a breach database (haveibeenpwned.com API implied by name) to retrieve information about whether an email appears in known data breaches. This has no side effects, creates no modifications, and triggers no external operations beyond data retrieval.
From the tool's definition Tool description states 'Check if an email account has been in a data breach' - this is a query/lookup operation that retrieves breach information without modifying any data or triggering side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs hibp_check_account safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hibp_check_account, this is the rule to start with:
hibp_check_account 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 UnClick, apply this rule, and every hibp_check_account call is checked against it from then on.
Questions about hibp_check_account
Check if an email account has been in a data breach. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
hibp_check_account accepts 2 parameters: email, api_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for hibp_check_account: 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 UnClick. Nothing to install.
hibp_check_account 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 hibp_check_account 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 hibp_check_account. 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.
hibp_check_account is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue