no_portscan
Perform host discovery without port scanning on the specified target with optional custom arguments.
This record as markdown: /tools/0xpratikpatil-nmapmcp/no-portscan.md
What no_portscan does on NmapMCP
AI agents invoke no_portscan 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 no_portscan is rated High
This tool performs active network reconnaissance (host discovery) against a specified target. While it doesn't scan ports, it still executes outbound network probes to discover live hosts. This is an external operation whose effects depend on the target argument, fitting the Execute category. Misuse could facilitate unauthorized reconnaissance of networks, hence medium severity.
From the tool's definition 'Perform host discovery without port scanning on the specified target' — actively probes/scans a network target, triggering external network operations
Attacks that exploit this kind of access
The rule that runs no_portscan 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 no_portscan, this is the rule to start with:
no_portscan 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 no_portscan call is checked against it from then on.
Questions about no_portscan
Perform host discovery without port scanning 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 no_portscan: 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.
no_portscan 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 no_portscan 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 no_portscan. 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.
no_portscan 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