Read-only DKIM selector discovery for a domain. Queries ~150 common selectors used by Google, Microsoft, Mailgun, SendGrid, Postmark, Amazon SES, Brevo, MailChimp, Zoho, and other major ESPs. Returns each discovered selector with parsed key tags (v, k, t, p), public key length, algorithm strength...
AI agents call discover_dkim 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 purely retrieves and analyzes publicly available DNS DKIM records for a domain. It has no side effects, creates no modifications, executes no code or external operations, and cannot delete or move money. The worst-case misuse is reconnaissance of email security infrastructure, which has low blast radius. The 'no auth required' and 'read-only' designation confirms its passive information-gathering nature.
From the tool's definition Tool description explicitly states 'Read-only DKIM selector discovery' and 'Queries ~150 common selectors...Returns each discovered selector with parsed key tags'.
Attacks that exploit this kind of access
Read-only DKIM selector discovery for a domain. Queries ~150 common selectors used by Google, Microsoft, Mailgun, SendGrid, Postmark, Amazon SES, Brevo, MailChimp, Zoho, and other major ESPs. Returns each discovered selector with parsed key tags (v, k, t, p), public key length, algorithm strength, and warnings (weak key, revoked, empty p=). Use when you do not know which DKIM selectors a domain publishes; use check_email_security for combined SPF/DKIM/DMARC overview. No auth, ~3-8s due to many parallel DNS queries. 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 discover_dkim: 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.
discover_dkim 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 discover_dkim 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 discover_dkim. 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.
discover_dkim 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 →