Validate an email address for deliverability and retrieve associated company information. Provides detailed analysis of email validity, MX records, and catch-all detection.
AI agents call validate_email to retrieve information from LeadMagic 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 external email validation services and retrieves associated company data. It has no capacity to modify, delete, execute code, or trigger financial transactions. The validation process is informational—analyzing MX records and deliverability—which is a read operation.
From the tool's definition Tool performs validation and retrieval of email deliverability status and associated company information. Keywords indicate read-only operations: 'Validate', 'retrieve', 'analysis' of existing email data without modification.
Documented attack patterns abuse exactly the kind of access validate_email gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LeadMagic MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for validate_email:
{
"version": "1",
"default": "deny",
"tools": {
"validate_email": {}
}
}validate_email is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Validate an email address for deliverability and retrieve associated company information. Provides detailed analysis of email validity, MX records, and catch-all detection. It is categorised as a Read tool in the LeadMagic MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LeadMagic MCP Server MCP server in PolicyLayer and add a rule for validate_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 LeadMagic MCP Server. Nothing to install.
validate_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 validate_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 validate_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.
validate_email is provided by the LeadMagic MCP Server MCP server (leadmagic/leadmagic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LeadMagic MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
19 LeadMagic MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.