AI agents call hunter_verify_email to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | Yes | |
api_key | string | — |
Parameters from the server's own tool schema.
Email verification is a read-only operation that queries Hunter.io's database to check if an email address is valid. It retrieves information without creating, modifying, deleting, or executing operations. No side effects or irreversible actions occur. Severity is low as the blast radius of misuse is limited to information leakage about email validity.
From the tool's definition Tool name 'hunter_verify_email' and description 'Verify an email address with Hunter.io' indicate a query/lookup operation that retrieves verification status without modifying data.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
Verify an email address with Hunter.io. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
hunter_verify_email accepts 2 parameters: email, api_key. Required: email. 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 hunter_verify_email: 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.
hunter_verify_email 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 hunter_verify_email 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 hunter_verify_email. 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.
hunter_verify_email 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.
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 →