nmap_scan

Run nmap in quick, aggressive, port, script, or custom mode.

SERVERHercules MCP SOURCE0xmihirk/hercules-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xmihirk-hercules-mcp/nmap-scan.md

WHAT IT DOES

What nmap_scan does on Hercules MCP

AI agents invoke nmap_scan to trigger actions in Hercules MCP. 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.

RISK

Why nmap_scan is rated High

This tool executes nmap network scanning commands against target systems. Network scanning is an active external operation that probes hosts and services. The 'aggressive' and 'custom' modes especially can trigger IDS/IPS alerts, disrupt services, or facilitate further attacks. Misuse by an AI agent could result in unauthorized reconnaissance against arbitrary targets, making severity high.

From the tool's definition 'Run nmap' in 'quick, aggressive, port, script, or custom mode' within a 'containerized Kali Linux environment' exposing 'offensive security tools'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs nmap_scan safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hercules MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nmap_scan, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Hercules MCP, apply this rule, and every nmap_scan call is checked against it from then on.

FAQ

Questions about nmap_scan

What does the nmap_scan tool do? +

Run nmap in quick, aggressive, port, script, or custom mode. It is categorised as a Execute tool in the Hercules MCP 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 Hercules 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 Hercules MCP. 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 Hercules MCP server (0xmihirk/hercules-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hercules, and thousands of servers like it.

This server

All 45 Hercules tools → High-risk tools on this server →

Across the catalogue

run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →