Perform network scan using nmap
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 a live network scanning tool that sends packets to external hosts. While it is primarily a reconnaissance/read operation, it actively runs code/commands against external systems, qualifying it as Execute. Misuse could involve scanning unauthorized networks, triggering IDS alerts, or being used as a precursor to exploitation.
From the tool's definition 'Perform network scan using nmap' — actively runs the nmap tool against network targets, triggering external network operations whose effects depend on arguments (scan type, target range, port selection).
Attacks that exploit this kind of access
Perform network scan using nmap. 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 (pellax/kalimcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →