# container_start

Start the Kali Linux Docker container. Must be called before running any commands.

Agent View of the PolicyLayer registry record for `container_start`. HTML page: https://policylayer.com/tools/hannes221-kali-mcp/container-start

## Facts

- Tool: `container_start`
- Server: Kali (`hannes221/kali-mcp`) — https://policylayer.com/tools/hannes221-kali-mcp.md
- Homepage: https://github.com/Hannes221/kali-mcp
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "container_start",
    "arguments": {}
  }
}
```

## 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 own 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…"

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Kali:

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

## Other tools on Kali (6)

- `container_stop` — Destructive — https://policylayer.com/tools/hannes221-kali-mcp/container-stop.md
- `execute_command` — Execute — https://policylayer.com/tools/hannes221-kali-mcp/execute-command.md
- `container_status` — Read — https://policylayer.com/tools/hannes221-kali-mcp/container-status.md
- `download_file` — Read — https://policylayer.com/tools/hannes221-kali-mcp/download-file.md
- `list_files` — Read — https://policylayer.com/tools/hannes221-kali-mcp/list-files.md
- `upload_file` — Write — https://policylayer.com/tools/hannes221-kali-mcp/upload-file.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=hannes221-kali-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/hannes221-kali-mcp