Query TXT records for a domain (includes SPF, DKIM, DMARC, verification records)
AI agents call query_txt_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 only retrieves DNS TXT record data for a given domain. It performs a read-only lookup operation with no side effects, data modification, code execution, or destructive capabilities. While TXT records may contain sensitive configuration information, the action itself is passive information retrieval, making it Read category with low severity due to minimal direct impact from misuse.
From the tool's definition Tool queries TXT records (SPF, DKIM, DMARC, verification records) without modifying data. The description explicitly lists query operations that retrieve information about DNS records.
Attacks that exploit this kind of access
Query TXT records for a domain (includes SPF, DKIM, DMARC, verification records). 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_txt_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_txt_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_txt_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_txt_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_txt_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 →