Scan a network/IP range for all open ports. If mulitple targets are provided and they are not in CIDR format, they should be space-separated.
AI agents invoke all_ports_scan_network to trigger actions in Nmap. 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.
This tool executes active network reconnaissance (Nmap all-ports scan) against potentially external targets. It triggers real network traffic and probes, which constitutes execution of external operations. Misuse could involve scanning unauthorized networks (illegal in many jurisdictions), revealing attack surface, or being used as a precursor to exploitation.
From the tool's definition 'Scan a network/IP range for all open ports' — actively runs Nmap port scanning operations against external hosts/networks
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access all_ports_scan_network gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nmap, and nothing reaches the server without passing your rules. This is the rule we recommend for all_ports_scan_network:
{
"version": "1",
"default": "deny",
"tools": {
"all_ports_scan_network": {
"limits": [
{
"counter": "all_ports_scan_network_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}all_ports_scan_network 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.
Free to start. No card required.
Scan a network/IP range for all open ports. If mulitple targets are provided and they are not in CIDR format, they should be space-separated. It is categorised as a Execute tool in the Nmap 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 all_ports_scan_network: 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 Nmap. Nothing to install.
all_ports_scan_network 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 all_ports_scan_network 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 all_ports_scan_network. 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.
all_ports_scan_network is provided by the Nmap MCP server (jarrodcoulter/nmap-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nmap, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Nmap tools catalogued and risk-classified — across an index of 43,000+ MCP servers.