AI agents call container_status to retrieve information from Kali without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about a Docker container without creating, modifying, deleting, or executing any operations. It is a pure read operation comparable to checking the state of a system resource. The low severity reflects minimal risk—an agent cannot cause harm by querying container status.
From the tool's 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 with no modifications or side effects.
Attacks that exploit this kind of access
Check the status of the Kali Linux Docker container. It is categorised as a Read tool in the Kali MCP Server, which means it retrieves data without modifying state.
Register the Kali MCP server in PolicyLayer and add a rule for container_status: 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_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the container_status 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_status. 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_status 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →