udp_scan

Perform a UDP scan on the specified target with optional custom arguments.

SERVERNmapMCP SOURCE0xpratikpatil/nmapmcp

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/0xpratikpatil-nmapmcp/udp-scan.md

WHAT IT DOES

What udp_scan does on NmapMCP

AI agents invoke udp_scan to trigger actions in NmapMCP. 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 udp_scan is rated High

UDP scanning actively probes remote hosts by sending network packets, which constitutes an external operation with real-world effects (network traffic, potential IDS alerts, legal implications). It is not merely reading local data but executing active reconnaissance against targets. Classified as Execute with high severity due to the potential for misuse against unauthorized targets.

From the tool's definition 'Perform a UDP scan on the specified target' — actively sends UDP packets to external hosts; part of a network reconnaissance MCP server

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs udp_scan safely

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

udp_scan Rate-limited

udp_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": {
    "udp_scan": {
      "limits": [
        {
          "counter": "udp_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 NmapMCP, apply this rule, and every udp_scan call is checked against it from then on.

FAQ

Questions about udp_scan

What does the udp_scan tool do? +

Perform a UDP scan on the specified target with optional custom arguments. It is categorised as a Execute tool in the NmapMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on udp_scan? +

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

What risk level is udp_scan? +

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

Can I rate-limit udp_scan? +

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

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

udp_scan is provided by the Nmap MCP server (0xpratikpatil/nmapmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nmap, and thousands of servers like it.

This server

All 15 Nmap 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 →