execute_command
Execute a shell command inside the Kali Linux container. Use this to run security tools like nmap, sqlmap, hydra, nikto, gobuster, john, hashcat, dirb, enum4linux, and any other installed tool.
This record as markdown: /tools/hannes221-kali-mcp/execute-command.md
What execute_command does on Kali
AI agents invoke execute_command to trigger actions in Kali. 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 execute_command is rated High
This tool enables unrestricted execution of arbitrary shell commands within a containerized penetration testing environment. An AI agent misusing this could run destructive commands (rm -rf), exfiltrate data, pivot to other systems, establish persistence, or launch attacks. While the server is intended for authorized security testing, the blast radius of command execution abuse is critical.
From the tool's definition Tool directly executes arbitrary shell commands in a full Kali Linux environment, explicitly mentioning security tools like nmap, sqlmap, hydra, metasploit, and others.
Attacks that exploit this kind of access
The rule that runs execute_command safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kali, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For execute_command, this is the rule to start with:
execute_command 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 Kali, apply this rule, and every execute_command call is checked against it from then on.
Questions about execute_command
Execute a shell command inside the Kali Linux container. Use this to run security tools like nmap, sqlmap, hydra, nikto, gobuster, john, hashcat, dirb, enum4linux, and any other installed tool. It is categorised as a Execute tool in the Kali MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali MCP server in PolicyLayer and add a rule for execute_command: 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. Nothing to install.
execute_command 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 execute_command 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 execute_command. 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.
execute_command is provided by the Kali MCP server (hannes221/kali-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Kali, and thousands of servers like it.
This server
Across the catalogue