Perform comprehensive DNS lookups for all record types
AI agents call dns_records to retrieve information from MCP Recon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
DNS lookups are passive information gathering operations that retrieve existing DNS records. They do not modify, delete, or execute any operations—they simply query and return data. This is a standard reconnaissance activity with no destructive or operational side effects. The severity is low because DNS record information is typically public and the tool poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'dns_records' and description 'Perform comprehensive DNS lookups for all record types' indicate querying/retrieval of DNS information without modification, deletion, or execution of commands.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access dns_records gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Recon, and nothing reaches the server without passing your rules. This is the rule we recommend for dns_records:
{
"version": "1",
"default": "deny",
"tools": {
"dns_records": {}
}
}dns_records is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Perform comprehensive DNS lookups for all record types. It is categorised as a Read tool in the MCP Recon MCP Server, which means it retrieves data without modifying state.
Register the MCP Recon MCP server in PolicyLayer and add a rule for dns_records: 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 MCP Recon. Nothing to install.
dns_records 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 dns_records 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 dns_records. 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.
dns_records is provided by the MCP Recon MCP server (sundayz-hunter/mcp_recon). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Recon, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 MCP Recon tools catalogued and risk-classified — across an index of 43,000+ MCP servers.