Attempt to perform a DNS zone transfer (AXFR) to enumerate all DNS records.
AI agents invoke attempt_zone_transfer to trigger actions in External Reconnaissance MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
A DNS zone transfer (AXFR) is an active network operation that queries an external DNS server, potentially exposing all internal DNS records of a target domain. It goes beyond passive reading — it executes a specific protocol request against a remote system.
From the tool's definition 'Attempt to perform a DNS zone transfer (AXFR)' — actively initiates a network operation against an external DNS server to retrieve all DNS records
Documented attack patterns abuse exactly the kind of access attempt_zone_transfer gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and External Reconnaissance MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for attempt_zone_transfer:
{
"version": "1",
"default": "deny",
"tools": {
"attempt_zone_transfer": {
"limits": [
{
"counter": "attempt_zone_transfer_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}attempt_zone_transfer stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Attempt to perform a DNS zone transfer (AXFR) to enumerate all DNS records. It is categorised as a Execute tool in the External Reconnaissance MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the External Reconnaissance MCP Server MCP server in PolicyLayer and add a rule for attempt_zone_transfer: 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 External Reconnaissance MCP Server. Nothing to install.
attempt_zone_transfer is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the attempt_zone_transfer 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 attempt_zone_transfer. 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.
attempt_zone_transfer is provided by the External Reconnaissance MCP Server MCP server (naebo/mcp-external-recon-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from External Reconnaissance MCP Server, 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.
8 External Reconnaissance MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.