AI agents call propagation_check to retrieve information from Idig Dns without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs DNS lookups and diagnostics across multiple public resolvers to diagnose propagation status. It is purely informational, retrieving data about DNS state without side effects. No data is created, modified, deleted, or financial operations are involved. This is a standard Read category operation, with low severity since misuse would only expose DNS information already publicly queryable.
From the tool's definition Tool description states it 'Check[s] DNS propagation across 16 global resolvers' — a query operation that retrieves and reports DNS data without modifying any records or systems.
Attacks that exploit this kind of access
Check DNS propagation across 16 global resolvers: Google, Cloudflare, Quad9, China, Korea, Russia. It is categorised as a Read tool in the Idig Dns MCP Server, which means it retrieves data without modifying state.
Register the Idig Dns MCP server in PolicyLayer and add a rule for propagation_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 Idig Dns. Nothing to install.
propagation_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 propagation_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 propagation_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.
propagation_check is provided by the Idig Dns MCP server (https://mcp.softricks.net/sse). 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 →