udp_scan
Perform a UDP scan on the specified target with optional custom arguments.
This record as markdown: /tools/0xpratikpatil-nmapmcp/udp-scan.md
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.
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
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 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.
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.
Questions about udp_scan
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.
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.
udp_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
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.
More on Nmap, and thousands of servers like it.
This server
Across the catalogue