Launch a Nmap scan against the given target with optional arguments.
AI agents invoke launch_nmap_scan to trigger actions in pentestMCP. 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 is Execute rather than Read because Nmap scans trigger active network operations and observable side effects beyond passive data retrieval. While reconnaissance itself is not destructive, the tool executes external commands whose behavior depends entirely on user-supplied arguments, making it dangerous if an AI agent receives adversarial instructions.
From the tool's definition Tool name 'launch_nmap_scan' and description state it 'Launch[es] a Nmap scan against the given target with optional arguments.' Nmap is a network reconnaissance tool that actively probes target systems and networks, triggering observable side effects…
Documented attack patterns abuse exactly the kind of access launch_nmap_scan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and pentestMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for launch_nmap_scan:
{
"version": "1",
"default": "deny",
"tools": {
"launch_nmap_scan": {
"limits": [
{
"counter": "launch_nmap_scan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}launch_nmap_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.
Free to start. No card required.
Launch a Nmap scan against the given target with optional arguments. It is categorised as a Execute tool in the pentestMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the pentest MCP server in PolicyLayer and add a rule for launch_nmap_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 pentestMCP. Nothing to install.
launch_nmap_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 launch_nmap_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 launch_nmap_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.
launch_nmap_scan is provided by the pentest MCP server (ramkansal/pentestmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 pentestMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 pentestMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.