Check email security configuration for any domain. Analyzes SPF, DMARC, DKIM (probes 10 common selectors), and MX records with provider detection. Free preview: GET https://email-security.apimesh.xyz/preview?domain=... checks SPF and DMARC for free
AI agents call email_security 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.
The email_security tool performs passive reconnaissance of email infrastructure configuration by querying public DNS records (SPF, DMARC, DKIM, MX). No side effects occur; it retrieves and reports existing configuration state. While the tool probes multiple selectors and enriches data, the core action is data retrieval.
From the tool's definition Tool description indicates it 'analyzes SPF, DMARC, DKIM...and MX records' and 'checks SPF and DMARC for free'—these are informational DNS lookups and email configuration audits that retrieve and query existing data without modifying or executing operations.
Attacks that exploit this kind of access
Check email security configuration for any domain. Analyzes SPF, DMARC, DKIM (probes 10 common selectors), and MX records with provider detection. Free preview: GET https://email-security.apimesh.xyz/preview?domain=... checks SPF and DMARC 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_security: 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_security 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_security 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_security. 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_security 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.
email_security is one line of APIMesh MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →