AI agents call dns_propagation_check to retrieve information from Infra Ops without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries DNS information from public servers to assess propagation status. It performs no writes, deletions, code execution, or financial operations. The blast radius of misuse is minimal—worst case, an agent performs excessive DNS queries against public servers, which is a read-only reconnaissance action with no impact on infrastructure or data integrity.
From the tool's definition Tool name 'dns_propagation_check' and description 'Check DNS propagation across multiple public DNS servers' indicate a query/diagnostic operation that retrieves DNS resolution data without modifying any records or triggering external actions.
Attacks that exploit this kind of access
Check DNS propagation across multiple public DNS servers. It is categorised as a Read tool in the Infra Ops MCP Server, which means it retrieves data without modifying state.
Register the Infra Ops MCP server in PolicyLayer and add a rule for dns_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 Infra Ops. Nothing to install.
dns_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 dns_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 dns_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.
dns_propagation_check is provided by the Infra Ops MCP server (skyvanguard/infra-ops-mcp). 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 →