Validate email authentication for a domain. Checks SPF, DKIM (common selectors), DMARC policy, and MX records. Detects spoofing vulnerabilities.
AI agents call email_headers to retrieve information from Mcp Services 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 publicly available DNS records and email configuration data. While it detects security vulnerabilities, it does not execute code, modify data, delete anything, or trigger external operations. The action is purely informational/analytical—querying and reading email authentication metadata.
From the tool's definition Tool performs validation and checking of email authentication records (SPF, DKIM, DMARC, MX records) without modifying or executing external operations. The description uses purely passive verbs: 'Validate', 'Checks', 'Detects'.
Attacks that exploit this kind of access
Validate email authentication for a domain. Checks SPF, DKIM (common selectors), DMARC policy, and MX records. Detects spoofing vulnerabilities. It is categorised as a Read tool in the Mcp Services MCP Server, which means it retrieves data without modifying state.
Register the Mcp Services MCP server in PolicyLayer and add a rule for email_headers: 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 Mcp Services. Nothing to install.
email_headers 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_headers 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_headers. 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_headers is provided by the Mcp Services MCP server (san-npm/mcp-services). 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 →