Query AAAA records (IPv6 addresses) for a domain
AI agents call query_aaaa_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.
The tool retrieves DNS record information without side effects. AAAA record queries are read-only operations that return publicly available DNS data. No data is modified, deleted, or executed, and there are no financial implications. The blast radius of misuse is minimal—an attacker could only gather reconnaissance information about a target's IPv6 infrastructure, which is already public DNS data.
From the tool's definition Tool description states it 'Query[s] AAAA records (IPv6 addresses) for a domain' — a pure DNS query operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Query AAAA records (IPv6 addresses) 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_aaaa_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_aaaa_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_aaaa_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_aaaa_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_aaaa_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 →