hunter_verify_email
Verify an email address with Hunter.io.
This record as markdown: /tools/creativelead-unclick/hunter-verify-email.md
What hunter_verify_email does on UnClick
AI agents call hunter_verify_email 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 hunter_verify_email is rated Low
Email verification is fundamentally a read operation - it queries Hunter.io's database to validate whether an email address exists and is associated with a domain. No data is created, modified, or deleted.
From the tool's definition Tool description states 'Verify an email address with Hunter.io' - the core action is verification/validation of email data, which is a query operation that retrieves or checks information without modifying data.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs hunter_verify_email 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 hunter_verify_email, this is the rule to start with:
hunter_verify_email 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 hunter_verify_email call is checked against it from then on.
Questions about hunter_verify_email
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. 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 (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