Look up DKIM public keys at <selector>._domainkey.<domain>. Because DKIM selectors are arbitrary and undiscoverable, you should pass the selector(s) your mail provider uses for a definitive answer; otherwise a curated list of common selectors is probed and a miss is inconclusive. Args: - domain (...
AI agents call dkim_check to retrieve information from Domain Security without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries DNS records to audit email security configuration (DKIM public keys). It retrieves data without side effects, making it a Read operation. The blast radius is minimal—unauthorized DKIM lookups reveal only publicly available DNS records and do not modify systems, execute code, or commit financial actions.
From the tool's definition Tool 'dkim_check' performs DNS lookups at '<selector>._domainkey.<domain>' to retrieve DKIM public keys. The description states it 'looks up' keys and 'probes' selectors, with no mention of modification, deletion, or execution of commands.
Attacks that exploit this kind of access
Look up DKIM public keys at <selector>._domainkey.<domain>. Because DKIM selectors are arbitrary and undiscoverable, you should pass the selector(s) your mail provider uses for a definitive answer; otherwise a curated list of common selectors is probed and a miss is inconclusive. Args: - domain (string): the domain to check. - selectors (string[], optional): DKIM selectors to probe. - response_format (. It is categorised as a Read tool in the Domain Security MCP Server, which means it retrieves data without modifying state.
Register the Domain Security MCP server in PolicyLayer and add a rule for dkim_check: 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 Domain Security. Nothing to install.
dkim_check 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 dkim_check 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 dkim_check. 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.
dkim_check is provided by the Domain Security MCP server (ortamarco/domain-security-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 →