nmap_network_discovery · Nmap MCP Server MCP: Risk & Policy

WHAT IT DOES

What nmap_network_discovery does on Nmap MCP Server

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

Network discovery involves actively sending packets to enumerate live hosts and services across a network. This is an external operation with real effects (network traffic, potential IDS alerts, exposure of network topology). It falls under Execute because it triggers external network operations whose effects depend on the target arguments.

From the tool's definition 'Discover hosts and services on a network' — actively probes network infrastructure using Nmap scanning capabilities as described in the server description

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

nmap_network_discovery Rate-limited

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

FAQ

Questions about nmap_network_discovery

What does the nmap_network_discovery tool do? +

Discover hosts and services on a network. It is categorised as a Execute tool in the Nmap 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_network_discovery? +

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

What risk level is nmap_network_discovery? +

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

Can I rate-limit nmap_network_discovery? +

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

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

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