docker_bench_security_scan
A execute tool on the Pengstrike MCP server.
This record as markdown: /tools/pengstrike-mcp/docker-bench-security-scan.md
What docker_bench_security_scan does on Pengstrike
AI agents invoke docker_bench_security_scan to trigger actions in Pengstrike. 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.
Why docker_bench_security_scan is rated High
Docker Bench Security is a well-known shell script that runs checks against Docker daemon, images, containers, and host configurations. Despite the empty description, the name strongly implies execution of a security scanning script.
From the tool's definition Tool name: 'docker_bench_security_scan' — implies running Docker Bench for Security, a script that executes system-level security audits against Docker configurations.
Attacks that exploit this kind of access
The rule that runs docker_bench_security_scan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pengstrike, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For docker_bench_security_scan, this is the rule to start with:
docker_bench_security_scan stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Pengstrike, apply this rule, and every docker_bench_security_scan call is checked against it from then on.
Questions about docker_bench_security_scan
docker_bench_security_scan is a execute tool on the Pengstrike MCP server. It is categorised as a Execute tool in the Pengstrike MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pengstrike MCP server in PolicyLayer and add a rule for docker_bench_security_scan: 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 Pengstrike. Nothing to install.
docker_bench_security_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the docker_bench_security_scan 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_scan. 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_scan is provided by the Pengstrike MCP server (wangqiongpeng/pengstrike-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pengstrike, and thousands of servers like it.
Across the catalogue