scan_top_ports
Scan the top ports of the specified target with optional custom arguments.
This record as markdown: /tools/0xpratikpatil-nmapmcp/scan-top-ports.md
What scan_top_ports does on NmapMCP
AI agents invoke scan_top_ports 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 scan_top_ports is rated High
This tool executes network port scanning against specified targets, which is an active external operation. It can be used for reconnaissance against systems the operator may not own, carries legal and ethical risks, and the 'optional custom arguments' expand its attack surface. Classified as Execute (not Read) because it actively sends network packets to external systems rather than querying local data.
From the tool's definition 'Scan the top ports of the specified target with optional custom arguments' — triggers active network scanning against external targets
Attacks that exploit this kind of access
The rule that runs scan_top_ports 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 scan_top_ports, this is the rule to start with:
scan_top_ports 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 scan_top_ports call is checked against it from then on.
Questions about scan_top_ports
Scan the top ports of 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 scan_top_ports: 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.
scan_top_ports 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 scan_top_ports 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 scan_top_ports. 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.
scan_top_ports 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