run_nmap_scan · GhostMap v2 MCP: Risk & Policy

WHAT IT DOES

What run_nmap_scan does on GhostMap v2

AI agents invoke run_nmap_scan to trigger actions in GhostMap v2. 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_scan needs a policy

nmap is a network scanning tool that executes external commands whose effects depend on arguments (target hosts, ports, scan type). This is Execute category—it triggers external operations and retrieves results, but the effects are contingent on attacker-controlled parameters.

From the tool's definition Tool name 'run_nmap_scan' combined with server description stating it 'exposes...network reconnaissance' capabilities including 'host discovery, service fingerprinting' and sibling tools like 'run_arp_scan', 'run_hydra', and 'spoof_mac' clearly indicate…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_nmap_scan Rate-limited

run_nmap_scan 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_scan": {
      "limits": [
        {
          "counter": "run_nmap_scan_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 GhostMap v2, so you can run agents against it safely.

FAQ

Questions about run_nmap_scan

What does the run_nmap_scan tool do? +

run_nmap_scan. It is categorised as a Execute tool in the GhostMap v2 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_scan? +

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

What risk level is run_nmap_scan? +

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

Can I rate-limit run_nmap_scan? +

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

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

run_nmap_scan is provided by the GhostMap v2 MCP server (samir12218415/ghostmap-v2-ai-augmented-recon-framework-with-mcp-and-cve-pipeline). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.