AI agents invoke recon_ng_run to trigger actions in Kali Security MCP. 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 recon-ng, a reconnaissance framework that runs automated information gathering against targets. While reconnaissance itself may not be immediately destructive, executing external reconnaissance tools constitutes executing code/commands whose effects depend on what reconnaissance modules and targets are specified.
From the tool's definition Tool description states 'Execute recon-ng for reconnaissance.' The verb 'Execute' combined with 'recon-ng' (a reconnaissance framework that runs external tools, queries databases, and performs network reconnaissance) indicates this tool triggers external…
Documented attack patterns abuse exactly the kind of access recon_ng_run gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kali Security MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for recon_ng_run:
{
"version": "1",
"default": "deny",
"tools": {
"recon_ng_run": {
"limits": [
{
"counter": "recon_ng_run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}recon_ng_run 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.
Execute recon-ng for reconnaissance. It is categorised as a Execute tool in the Kali Security MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali Security MCP server in PolicyLayer and add a rule for recon_ng_run: 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 Security MCP. Nothing to install.
recon_ng_run 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_ng_run 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_ng_run. 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_ng_run is provided by the Kali Security MCP server (seac-25/kali-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 249 Kali Security MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
249 Kali Security MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.