hunter_find_email

Find email addresses for a domain using Hunter.io.

SERVERUnClick SOURCEcreativelead/unclick

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/creativelead-unclick/hunter-find-email.md

WHAT IT DOES

What hunter_find_email does on UnClick

AI agents call hunter_find_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
`domain`	string	—
`api_key`	string	—
`last_name`	string	—
`first_name`	string	—

Parameters from the server's own tool schema.

RISK

Why hunter_find_email is rated Low

This tool queries an external service (Hunter.io) to retrieve email addresses associated with a domain. It performs a read-only lookup operation with no side effects on data creation, modification, or destruction.

From the tool's definition Tool name 'hunter_find_email' and description 'Find email addresses for a domain' indicate retrieval of email data from Hunter.io API without modification or deletion.

Risk signalsHandles credentials or secrets (api_key)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hunter_find_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_find_email, this is the rule to start with:

hunter_find_email Allowed

hunter_find_email is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hunter_find_email": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every hunter_find_email call is checked against it from then on.

FAQ

Questions about hunter_find_email

What does the hunter_find_email tool do? +

Find email addresses for a domain using Hunter.io. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.

What parameters does hunter_find_email accept? +

hunter_find_email accepts 4 parameters: domain, api_key, last_name, first_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hunter_find_email? +

Register the UnClick MCP server in PolicyLayer and add a rule for hunter_find_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.

What risk level is hunter_find_email? +

hunter_find_email is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit hunter_find_email? +

Yes. Add a rate_limit block to the hunter_find_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.

How do I block hunter_find_email completely? +

Set action: deny in the PolicyLayer policy for hunter_find_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.

What MCP server provides hunter_find_email? +

hunter_find_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.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 451 UnClick tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →