Read-only fetch and parse of the _dmarc TXT record. Returns parsed tag map (p, sp, rua, ruf, adkim, aspf, pct, fo), policy strength assessment, alignment mode, and warnings (missing rua, p=none, weak alignment, multiple records). Use for DMARC policy review; use check_sender_requirements for comb...
AI agents call check_dmarc to retrieve information from Intodns without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only DNS query to retrieve and parse DMARC policy records. It retrieves data without modification, deletion, or triggering external actions. The description explicitly confirms 'Read-only', 'Single GET, no auth, no side effects', indicating purely informational retrieval with no side effects or capability to alter systems.
From the tool's definition Read-only fetch and parse of the _dmarc TXT record. Single GET, no auth, no side effects.
Attacks that exploit this kind of access
Read-only fetch and parse of the _dmarc TXT record. Returns parsed tag map (p, sp, rua, ruf, adkim, aspf, pct, fo), policy strength assessment, alignment mode, and warnings (missing rua, p=none, weak alignment, multiple records). Use for DMARC policy review; use check_sender_requirements for combined Google/Yahoo SPF+DKIM+DMARC pass/fail verdict. Single GET, no auth, no side effects. It is categorised as a Read tool in the Intodns MCP Server, which means it retrieves data without modifying state.
Register the Intodns MCP server in PolicyLayer and add a rule for check_dmarc: 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 Intodns. Nothing to install.
check_dmarc 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_dmarc 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_dmarc. 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_dmarc is provided by the Intodns MCP server (rosconl/intodns-mcp-server). 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 →