nmap · PenTest MCP Server MCP: Risk & Policy

WHAT IT DOES

What nmap does on PenTest MCP Server

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

nmap executes active network reconnaissance against potentially arbitrary targets. While it is primarily a read/reconnaissance tool, it sends packets to external systems, can trigger IDS alerts, may affect target availability with aggressive scans, and is explicitly part of a penetration testing server designed for security assessments.

From the tool's definition 'Port scanning and service detection' — nmap actively probes remote hosts by sending network packets, constituting an external operation whose effects (scan type, target, intensity) depend on arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

nmap Rate-limited

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

FAQ

Questions about nmap

What does the nmap tool do? +

Port scanning and service detection. It is categorised as a Execute tool in the 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 nmap? +

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

What risk level is nmap? +

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

Can I rate-limit nmap? +

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

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

nmap is provided by the PenTest MCP Server MCP server (mohitsahoo/mcptoolforwebvulnerabilities-). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.