Start the Kali Linux container if not running
AI agents invoke start_kali_container to trigger actions in Kali 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.
start_kali_container triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
Start the Kali Linux container if not running. It is categorised as a Execute tool in the Kali MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali MCP Server MCP server in PolicyLayer and add a rule for start_kali_container: 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 MCP Server. Nothing to install.
start_kali_container 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 start_kali_container 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 start_kali_container. 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.
start_kali_container is provided by the Kali MCP Server MCP server (vasanthadithya-mundrathi/kali-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.