# container_status

Check the status of the Kali Linux Docker container.

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

## Facts

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

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

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

## Why container_status is rated Low

This is a read-only operation that queries the status of a Docker container. It has no side effects, does not execute commands, and does not modify any data or state. The blast radius of misuse is minimal—an attacker gains only information about whether the container is running.

From the tool's own definition: "Tool name 'container_status' and description 'Check the status of the Kali Linux Docker container' indicate a query operation that retrieves container state information without modifying or executing anything."

## Use case

AI agents call container_status to retrieve information from Kali without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "container_status": {}
  }
}
```

## Other tools on Kali (6)

- `container_stop` — Destructive — https://policylayer.com/tools/hannes221-kali-mcp/container-stop.md
- `container_start` — Execute — https://policylayer.com/tools/hannes221-kali-mcp/container-start.md
- `execute_command` — Execute — https://policylayer.com/tools/hannes221-kali-mcp/execute-command.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