Docker security best practices checker based on CIS benchmark.
AI agents call docker_bench_security to retrieve information from MCP Kali Pentest without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and analyzes Docker daemon configurations and running containers to identify security misconfigurations. It produces reports on compliance with CIS benchmarks but does not modify Docker settings, execute commands inside containers, or alter system state. The blast radius of misuse is minimal—worst case would be false reporting of security status.
From the tool's definition Docker Bench Security is a checker tool that evaluates Docker configurations against CIS benchmark best practices.
Attacks that exploit this kind of access
Docker security best practices checker based on CIS benchmark. It is categorised as a Read tool in the MCP Kali Pentest MCP Server, which means it retrieves data without modifying state.
Register the MCP Kali Pentest MCP server in PolicyLayer and add a rule for docker_bench_security: 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 MCP Kali Pentest. Nothing to install.
docker_bench_security 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 docker_bench_security 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 docker_bench_security. 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.
docker_bench_security is provided by the MCP Kali Pentest MCP server (root1856/mcpkali). 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 →