fast_reconnaissance

What fast_reconnaissance does on Kali Security MCP

AI agents invoke fast_reconnaissance 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.

Why fast_reconnaissance is rated High

Reconnaissance workflows actively scan, probe, and query external targets using Kali Linux tools (e.g., nmap, recon-ng). This is not a passive read — it triggers automated external network operations against targets. On a penetration testing platform, misuse could expose unauthorized scanning of systems, making it Execute with high severity.

From the tool's definition 'fast_reconnaissance' on a server integrating 193 Kali Linux security tools for 'penetration testing' and 'vulnerability assessment through automated workflows' — description translates to 'Execute fast reconnaissance workflow'

The rule that runs fast_reconnaissance safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Kali Security MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fast_reconnaissance, this is the rule to start with:

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

Questions about fast_reconnaissance