quick_recon · Kali Pentest MCP Server MCP: Risk & Policy

WHAT IT DOES

What quick_recon does on Kali Pentest MCP Server

AI agents invoke quick_recon to trigger actions in Kali Pentest 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 quick_recon needs a policy

This tool executes reconnaissance commands against network targets. Even though restricted to whitelisted targets and for authorized testing, it triggers external operations (port scanning, web vulnerability assessment, database testing) whose outcomes depend on runtime arguments and cannot be fully predicted in advance.

From the tool's definition Tool runs 'quick reconnaissance scan combining multiple tools' on target systems, which involves executing external security testing tools (nmap, nikto, dirb, wpscan, sqlmap) whose effects depend on the target argument and tool configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

quick_recon Rate-limited

quick_recon 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": {
    "quick_recon": {
      "limits": [
        {
          "counter": "quick_recon_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 Pentest MCP Server, so you can run agents against it safely.

FAQ

Questions about quick_recon

What does the quick_recon tool do? +

Run quick reconnaissance scan combining multiple tools on whitelisted target. It is categorised as a Execute tool in the Kali Pentest 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 quick_recon? +

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

What risk level is quick_recon? +

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

Can I rate-limit quick_recon? +

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

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

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