local_nmap · Net MCP: Risk & Policy

WHAT IT DOES

What local_nmap does on Net

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

nmap is a network scanning and reconnaissance tool that actively probes hosts and networks. Running nmap constitutes executing an external tool with side effects (sending network packets to potentially arbitrary targets). Misuse could include scanning unauthorized networks, triggering IDS/IPS alerts, or violating terms of service. The 'local_' prefix suggests it runs on the host system.

From the tool's definition Tool name 'local_nmap' implies execution of the nmap network scanning utility locally. Description is empty and uninformative, lowering confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

local_nmap Rate-limited

local_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": {
    "local_nmap": {
      "limits": [
        {
          "counter": "local_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 Net, so you can run agents against it safely.

FAQ

Questions about local_nmap

What does the local_nmap tool do? +

local_nmap. It is categorised as a Execute tool in the Net MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on local_nmap? +

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

What risk level is local_nmap? +

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

Can I rate-limit local_nmap? +

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

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

local_nmap is provided by the Net MCP server (steelcutoatmeal/net-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.