Automated multi-stage reconnaissance pipeline (DNS, ports, headers, SSL, exploits)
AI agents invoke recon_auto 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.
This tool executes a multi-stage automated pipeline combining DNS enumeration, port scanning, HTTP header analysis, SSL inspection, and exploit searching against target systems. It actively probes external systems, which constitutes execution of network operations with real side effects.
From the tool's definition Automated multi-stage reconnaissance pipeline (DNS, ports, headers, SSL, exploits)
Documented attack patterns abuse exactly the kind of access recon_auto gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kali MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for recon_auto:
{
"version": "1",
"default": "deny",
"tools": {
"recon_auto": {
"limits": [
{
"counter": "recon_auto_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}recon_auto 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.
Automated multi-stage reconnaissance pipeline (DNS, ports, headers, SSL, exploits). 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.
Register the Kali MCP Server MCP server in PolicyLayer and add a rule for recon_auto: 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.
recon_auto 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 recon_auto 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 recon_auto. 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.
recon_auto is provided by the Kali MCP Server MCP server (k3nn3dy-ai/kali-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kali 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.
36 Kali MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.