AI agents invoke nmap_scan to trigger actions in Kali Linux MCP Server. 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.
nmap_scan executes network reconnaissance against target hosts/networks. Running in a privileged Docker container on a Kali Linux pentest server, this tool can perform active network scanning, OS fingerprinting, and service discovery. Misuse by an AI agent could trigger scans against unauthorized targets, violate computer fraud laws, or expose internal network topology.
From the tool's definition Tool name 'nmap_scan' on a server described as providing 'network scanning (nmap)' via a 'privileged Docker container' for 'penetration testing tools'
Documented attack patterns abuse exactly the kind of access nmap_scan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kali Linux MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for nmap_scan:
{
"version": "1",
"default": "deny",
"tools": {
"nmap_scan": {
"limits": [
{
"counter": "nmap_scan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
nmap_scan. It is categorised as a Execute tool in the Kali Linux MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali Linux MCP Server MCP server in PolicyLayer and add a rule for 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 Kali Linux MCP Server. Nothing to install.
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 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 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.
nmap_scan is provided by the Kali Linux MCP Server MCP server (marklechner/kali-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kali Linux MCP Server, 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.
7 Kali Linux MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.