Query NS records (nameservers) for a domain
AI agents call query_ns_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 nameserver records for a domain, which is a read-only operation that queries existing data without side effects. It does not create, modify, delete, execute code, or involve financial transactions. The blast radius of misuse is minimal—an agent querying NS records poses no security risk beyond information gathering about publicly available DNS infrastructure.
From the tool's definition Tool name is 'query_ns_record' and description states 'Query NS records (nameservers) for a domain' — a pure query operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Query NS records (nameservers) 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_ns_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_ns_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_ns_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_ns_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_ns_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 →