container_start · Kali MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why container_start needs a policy

This tool triggers the startup of a Kali Linux container, which enables subsequent command execution and system operations. While the action itself is not destructive or financial, it is an Execute category tool because it initiates an external operational context (container startup) whose effects depend on what commands are run afterwards.

From the tool's definition Tool 'container_start' starts a Docker container; 'Must be called before running any commands' indicates it enables execution of external operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

container_start Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "container_start": {
      "limits": [
        {
          "counter": "container_start_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kali, so you can run agents against it safely.

FAQ

Questions about container_start

What does the container_start tool do? +

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.

How do I enforce a policy on container_start? +

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.

What risk level is container_start? +

container_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit container_start? +

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.

How do I block container_start completely? +

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.

What MCP server provides container_start? +

container_start is provided by the Kali MCP server (unaacceptable297/kali-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.