dnsrecon_scan · Kali MCP Server MCP: Risk & Policy

WHAT IT DOES

What dnsrecon_scan does on Kali MCP Server

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

WHY IT NEEDS A POLICY

Why dnsrecon_scan needs a policy

dnsrecon_scan performs active DNS enumeration against external targets, executing network reconnaissance operations. While it is read-like in nature (gathering DNS information), it runs an external tool that actively probes targets, qualifying it as Execute. On a penetration testing server alongside tools like hydra and sqlmap, misuse could facilitate unauthorized reconnaissance.

From the tool's definition DNS enumeration and scanning — part of a Kali Linux penetration testing toolset including tools like nmap, sqlmap, nikto, and hydra for 'authorized security testing and vulnerability assessment'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dnsrecon_scan Rate-limited

dnsrecon_scan 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_scan": {
      "limits": [
        {
          "counter": "dnsrecon_scan_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 Kali MCP Server, so you can run agents against it safely.

FAQ

Questions about dnsrecon_scan

What does the dnsrecon_scan tool do? +

DNS enumeration and scanning. It is categorised as a Execute tool in the Kali MCP Server 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_scan? +

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

What risk level is dnsrecon_scan? +

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

Can I rate-limit dnsrecon_scan? +

Yes. Add a rate_limit block to the dnsrecon_scan 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_scan completely? +

Set action: deny in the PolicyLayer policy for dnsrecon_scan. 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_scan? +

dnsrecon_scan is provided by the Kali MCP Server MCP server (jesseeikeland/kali-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.