hunter_domain_info
Get email information for a domain from Hunter.io.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/hunter-domain-info.md
What hunter_domain_info does on UnClick
AI agents call hunter_domain_info 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 |
|---|---|---|---|
domain | string | Yes | |
api_key | string | — |
Parameters from the server's own tool schema.
Why hunter_domain_info is rated Low
This tool queries and retrieves email contact information for a domain from Hunter.io's database. No data is modified, deleted, or created; it performs a simple GET/fetch operation. The returned information is typically public OSINT data. Severity is low as misuse would only expose already-available contact information without unintended consequences.
From the tool's definition Tool name 'hunter_domain_info' and description 'Get email information for a domain' indicate data retrieval with no side effects. Hunter.io is a public email lookup service.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs hunter_domain_info 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_domain_info, this is the rule to start with:
hunter_domain_info 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_domain_info call is checked against it from then on.
Questions about hunter_domain_info
Get email information for a domain from Hunter.io. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
hunter_domain_info accepts 2 parameters: domain, api_key. Required: domain. 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_domain_info: 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_domain_info 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_domain_info 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_domain_info. 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_domain_info 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