nmap_scan · Redteam MCP: Risk & Policy

WHAT IT DOES

What nmap_scan does on Redteam

AI agents invoke nmap_scan to trigger actions in Redteam. 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 executes active network reconnaissance by sending packets to target systems, which constitutes an external operation with real-world effects. On a red-team/pentest server designed for hacking, this tool can be used to probe unauthorized targets. While Nmap itself is primarily a scanner (Read-like), it executes OS-level commands and network probes against external systems, placing it in Execute.

From the tool's definition 'Run an Nmap scan against a target' on a 'penetration testing MCP server that runs 20 hacking tools inside a Kali Linux Docker container'

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 Redteam, so you can run agents against it safely.

FAQ

Questions about nmap_scan

What does the nmap_scan tool do? +

Run an Nmap scan against a target. It is categorised as a Execute tool in the Redteam 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 Redteam 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 Redteam. 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 Redteam MCP server (samirjani03/redteam-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.