run_nmap_discovery · Hacking Buddy MCP: Risk & Policy

WHAT IT DOES

What run_nmap_discovery does on Hacking Buddy MCP

AI agents invoke run_nmap_discovery to trigger actions in Hacking Buddy 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 IT NEEDS A POLICY

Why run_nmap_discovery needs a policy

This tool executes external commands (nmap network scanning) whose effects depend on arguments (the IP range specified). It is not a simple read operation since it actively probes network infrastructure and can trigger alerts/responses from target systems. It is not Destructive since it does not delete or overwrite data.

From the tool's definition Tool name 'run_nmap_discovery' combined with description 'Running nmap discovery scan of ip range' directly executes nmap, a network reconnaissance tool that performs active scanning operations on specified IP ranges.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_nmap_discovery Rate-limited

run_nmap_discovery 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": {
    "run_nmap_discovery": {
      "limits": [
        {
          "counter": "run_nmap_discovery_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 Hacking Buddy MCP, so you can run agents against it safely.

FAQ

Questions about run_nmap_discovery

What does the run_nmap_discovery tool do? +

Running nmap discovery scan of ip range. It is categorised as a Execute tool in the Hacking Buddy MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_nmap_discovery? +

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

What risk level is run_nmap_discovery? +

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

Can I rate-limit run_nmap_discovery? +

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

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

run_nmap_discovery is provided by the Hacking Buddy MCP server (manuelberrueta/hacking-buddy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.