portscan_only
Perform a port scan only on the specified target with optional custom arguments.
This record as markdown: /tools/0xpratikpatil-nmapmcp/portscan-only.md
What portscan_only does on NmapMCP
AI agents invoke portscan_only 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 portscan_only is rated High
Port scanning is an active network operation that sends packets to remote hosts to enumerate open ports. It triggers external operations whose effects depend on arguments (target host, port range, custom args).
From the tool's definition 'Perform a port scan only on the specified target with optional custom arguments' — actively executes network reconnaissance against external targets
Attacks that exploit this kind of access
The rule that runs portscan_only 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 portscan_only, this is the rule to start with:
portscan_only 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 portscan_only call is checked against it from then on.
Questions about portscan_only
Perform a port scan only 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 portscan_only: 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.
portscan_only 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 portscan_only 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 portscan_only. 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.
portscan_only 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