dnsrecon_enum · Redteam MCP: Risk & Policy

WHAT IT DOES

What dnsrecon_enum does on Redteam

AI agents invoke dnsrecon_enum to trigger actions in Redteam. 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.

WHY IT NEEDS A POLICY

Why dnsrecon_enum needs a policy

DNS reconnaissance actively queries external DNS infrastructure to enumerate records, subdomains, and topology of a target. This is an active operation with external side effects (network traffic directed at a target), running within a hacking-focused execution environment. It falls under Execute rather than Read because it triggers external network operations against third-party systems.

From the tool's definition Runs inside a Kali Linux Docker container enabling AI assistants to 'execute security scans and attacks'; tool performs 'DNS reconnaissance on a target domain'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dnsrecon_enum Rate-limited

dnsrecon_enum 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dnsrecon_enum": {
      "limits": [
        {
          "counter": "dnsrecon_enum_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Redteam, so you can run agents against it safely.

FAQ

Questions about dnsrecon_enum

What does the dnsrecon_enum tool do? +

Perform DNS reconnaissance on a target domain. It is categorised as a Execute tool in the Redteam MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on dnsrecon_enum? +

Register the Redteam MCP server in PolicyLayer and add a rule for dnsrecon_enum: 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 Redteam. Nothing to install.

What risk level is dnsrecon_enum? +

dnsrecon_enum is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit dnsrecon_enum? +

Yes. Add a rate_limit block to the dnsrecon_enum 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.

How do I block dnsrecon_enum completely? +

Set action: deny in the PolicyLayer policy for dnsrecon_enum. 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.

What MCP server provides dnsrecon_enum? +

dnsrecon_enum is provided by the Redteam MCP server (samirjani03/redteam-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.