AI agents call resolve_dns to retrieve information from Dns without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
DNS resolution is a read-only lookup operation that queries DNS records for a domain. It has no side effects and does not modify any data. The server context confirms this is a lookup/resolution service. Low severity as misuse only reveals publicly available DNS information.
From the tool's definition Tool name 'resolve_dns' and server description mentions 'DNS resolution' — the description itself is empty/uninformative.
Attacks that exploit this kind of access
resolve_dns. It is categorised as a Read tool in the Dns MCP Server, which means it retrieves data without modifying state.
Register the Dns MCP server in PolicyLayer and add a rule for resolve_dns: 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 Dns. Nothing to install.
resolve_dns 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 resolve_dns 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 resolve_dns. 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.
resolve_dns is provided by the Dns MCP server (r0bin2u/dns-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 →