Check if the container is running with necessary privileges for security tools.
AI agents call check_container_permissions to retrieve information from Kali Linux MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and reports on the container's privilege/permission status. It performs a diagnostic query with no side effects. However, the broader server context (privileged Docker container, pentest tools) elevates the blast radius slightly since understanding privilege levels could inform further attacks, but the tool itself only retrieves information.
From the tool's definition Check if the container is running with necessary privileges for security tools
Documented attack patterns abuse exactly the kind of access check_container_permissions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kali Linux MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_container_permissions:
{
"version": "1",
"default": "deny",
"tools": {
"check_container_permissions": {}
}
}check_container_permissions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check if the container is running with necessary privileges for security tools. It is categorised as a Read tool in the Kali Linux MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kali Linux MCP Server MCP server in PolicyLayer and add a rule for check_container_permissions: 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 Linux MCP Server. Nothing to install.
check_container_permissions 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 check_container_permissions 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 check_container_permissions. 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.
check_container_permissions is provided by the Kali Linux MCP Server MCP server (marklechner/kali-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kali Linux MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Kali Linux MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.