Query CNAME records (canonical name/alias) for a domain
AI agents call query_cname_record to retrieve information from DNS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves DNS CNAME records, which is a passive read operation that queries existing public DNS information. It has no side effects, does not modify data, and does not execute code or commands. The blast radius of misuse is minimal—an attacker could only enumerate DNS aliases to map network infrastructure, which is informational only.
From the tool's definition Tool name 'query_cname_record' and description 'Query CNAME records (canonical name/alias) for a domain' indicate read-only DNS record retrieval with no modification or deletion of data.
Attacks that exploit this kind of access
Query CNAME records (canonical name/alias) for a domain. It is categorised as a Read tool in the DNS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DNS MCP Server MCP server in PolicyLayer and add a rule for query_cname_record: 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 MCP Server. Nothing to install.
query_cname_record 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 query_cname_record 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 query_cname_record. 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.
query_cname_record is provided by the DNS MCP Server MCP server (stanibaj/dns-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 →