Validate DMARC, SPF, and DKIM records for a domain. Checks for common misconfigurations,
AI agents call check_email_auth to retrieve information from SiteHealth MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and validates existing email authentication configuration records via DNS queries. It performs no writes, deletes, executions, or financial operations. The blast radius of misuse is minimal — an attacker could only learn about a domain's email security posture, which is already public DNS data. Classification as Read is appropriate.
From the tool's definition Tool description states 'Validate DMARC, SPF, and DKIM records' and 'Checks for common misconfigurations' — purely diagnostic operations that query DNS records and email authentication policies. No mutation, deletion, or command execution occurs.
Attacks that exploit this kind of access
Validate DMARC, SPF, and DKIM records for a domain. Checks for common misconfigurations,. It is categorised as a Read tool in the SiteHealth MCP MCP Server, which means it retrieves data without modifying state.
Register the SiteHealth MCP server in PolicyLayer and add a rule for check_email_auth: 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 SiteHealth MCP. Nothing to install.
check_email_auth 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 check_email_auth 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 check_email_auth. 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.
check_email_auth is provided by the SiteHealth MCP server (sitehealth-mcp). 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 →