nmap_scan · Echo MCP Server MCP: Risk & Policy

WHAT IT DOES

What nmap_scan does on Echo MCP Server

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

Nmap performs active network reconnaissance by sending packets to target hosts and ports. Even though the description is empty, the tool name and server context (alongside tools like hydra_bruteforce and sqlmap_scan) make it clear this executes external network scanning operations. Misuse could enable unauthorized network reconnaissance, mapping internal infrastructure, or facilitating further attacks.

From the tool's definition Tool name 'nmap_scan' strongly implies execution of the Nmap network scanning tool. Sibling tools include offensive security tools like hydra_bruteforce, sqlmap_scan, nikto_scan, dirb_scan — confirming this is a penetration testing/security scanning server.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

nmap_scan Rate-limited

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

FAQ

Questions about nmap_scan

What does the nmap_scan tool do? +

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

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

What risk level is nmap_scan? +

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

Can I rate-limit nmap_scan? +

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

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

nmap_scan is provided by the Echo MCP Server MCP server (somacaru/mcp_setup). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.