AI agents call check_dns_propagation 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 retrieves and compares DNS data from public resolvers to analyze propagation status. It performs read-only queries with no side effects, no data modification, and no code execution. The blast radius of misuse is minimal—an agent could only query DNS records, which is non-destructive information gathering. This is a clear Read category tool.
From the tool's definition The tool 'compare[s] DNS responses across ~15-30 public resolvers worldwide' and 'detect[s] propagation lag or stale negative caches'. These are passive query operations with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Compare DNS responses across ~15-30 public resolvers worldwide to detect propagation lag or stale negative caches. Defaults to record type A, region. 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_dns_propagation: 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_dns_propagation 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_dns_propagation 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_dns_propagation. 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_dns_propagation 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 →