Find an email address using first name, last name, and domain information.
AI agents call hatch_find_email to retrieve information from Hatch 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 a database to retrieve contact information (email addresses). It is a pure read operation that retrieves data without modifying, deleting, or executing anything. Even if the email data is sensitive, the tool itself has no destructive or harmful execution capability — it simply searches and returns existing information.
From the tool's definition Tool description states 'Find an email address' — a retrieval operation with no side effects. Sibling tools (verify_email, find_company_data, find_phone, get_linkedin_url) are all lookup/query operations.
Attacks that exploit this kind of access
Find an email address using first name, last name, and domain information. It is categorised as a Read tool in the Hatch MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Hatch MCP Server MCP server in PolicyLayer and add a rule for hatch_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 Hatch MCP Server. Nothing to install.
hatch_find_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 hatch_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.
Set action: deny in the PolicyLayer policy for hatch_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.
hatch_find_email is provided by the Hatch MCP Server MCP server (meerkats-ai/hatch-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 →