hibp_check_password
Check if a password has appeared in a data breach.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/hibp-check-password.md
What hibp_check_password does on UnClick
AI agents call hibp_check_password 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 |
|---|---|---|---|
password | string | Yes |
Parameters from the server's own tool schema.
Why hibp_check_password is rated Low
This tool queries an external database to retrieve information about whether a password exists in known breaches. It performs no creation, modification, deletion, code execution, or financial operations. The misuse risk is low—an agent checking passwords against breach data causes no harm to systems or data, though it could reveal sensitivity about user accounts if used without authorization.
From the tool's definition Tool name 'hibp_check_password' and description 'Check if a password has appeared in a data breach' indicate a query/lookup operation against the Have I Been Pwned (HIBP) database.
Risk signalsHandles credentials or secrets (password)
Attacks that exploit this kind of access
The rule that runs hibp_check_password 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_password, this is the rule to start with:
hibp_check_password 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_password call is checked against it from then on.
Questions about hibp_check_password
Check if a password has appeared 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_password accepts 1 parameter: password. Required: password. 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_password: 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_password 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_password 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_password. 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_password is provided by the UnClick MCP server (@unclick/mcp-server). 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