Verify an email address: syntax validation, MX record check, disposable domain detection, role-address detection, free provider detection, and deliverability assessment. Free preview: GET https://email-verify.apimesh.xyz/preview?email=... checks syntax and disposable status for free
AI agents call email_verify to retrieve information from APIMesh MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes information about email addresses without creating, modifying, deleting, or executing any operations. It queries external systems (MX records, disposable domain lists) but does not alter data. While the full API is pay-per-call, the verification itself is a passive information retrieval operation.
From the tool's definition Tool performs 'syntax validation, MX record check, disposable domain detection, role-address detection, free provider detection, and deliverability assessment' — all read-only queries against external data sources (DNS records, domain databases).
Attacks that exploit this kind of access
Verify an email address: syntax validation, MX record check, disposable domain detection, role-address detection, free provider detection, and deliverability assessment. Free preview: GET https://email-verify.apimesh.xyz/preview?email=... checks syntax and disposable status for free. It is categorised as a Read tool in the APIMesh MCP Server MCP Server, which means it retrieves data without modifying state.
Register the APIMesh MCP Server MCP server in PolicyLayer and add a rule for email_verify: 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 APIMesh MCP Server. Nothing to install.
email_verify 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 email_verify 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 email_verify. 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.
email_verify is provided by the APIMesh MCP Server MCP server (mbeato/apimesh). 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 →