Know how many email addresses we have for a domain or a company.
AI agents call hunter_email_count to retrieve information from Hunter Io MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries existing data (email count statistics) without creating, modifying, deleting, or executing any operations. It is a simple informational lookup that returns metrics about available email records. No irreversible actions, financial transactions, or external command execution occur.
From the tool's definition Tool description states it retrieves a count of email addresses for a domain or company. The verb 'Know' and context of querying Hunter.io API indicates data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Know how many email addresses we have for a domain or a company. It is categorised as a Read tool in the Hunter Io MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Hunter Io MCP Server MCP server in PolicyLayer and add a rule for hunter_email_count: 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 Hunter Io MCP Server. Nothing to install.
hunter_email_count 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_email_count 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_email_count. 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_email_count is provided by the Hunter Io MCP Server MCP server (meerkats-ai/hunter-io-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 →