container_start
Start the Kali Linux Docker container. Must be called before running any commands.
This record as markdown: /tools/hannes221-kali-mcp/container-start.md
What container_start does on Kali
AI agents invoke container_start 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 container_start is rated High
This tool initiates execution of a containerized environment that enables arbitrary command execution via sibling tools like execute_command. While not directly destructive itself, it is a prerequisite for and enabler of all downstream Execute and Destructive actions on the Kali system.
From the tool's definition Tool starts a Docker container running Kali Linux with security tools (nmap, sqlmap, metasploit). Starting a container is an operational action that triggers external system behavior—spinning up a full penetration testing environment with network access and…
Attacks that exploit this kind of access
The rule that runs container_start 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 container_start, this is the rule to start with:
container_start 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 container_start call is checked against it from then on.
Questions about container_start
Start the Kali Linux Docker container. Must be called before running any commands. 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 container_start: 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.
container_start 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 container_start 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 container_start. 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.
container_start 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