docker_security_audit

Inspect containers for risky runtime settings without changing anything.

SERVERMcp Control Plane SOURCEalbertik322-sudo/mcp-control-plane

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-control-plane/docker-security-audit.md

WHAT IT DOES

What docker_security_audit does on Mcp Control Plane

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

RISK

Why docker_security_audit is rated Low

The tool performs auditing and inspection of Docker containers to identify security issues. The phrase 'without changing anything' confirms this is a non-destructive, non-modifying operation. No data is created, modified, deleted, or financial transactions occur. This is purely a query/inspection operation, making it a Read category tool with low severity risk.

From the tool's definition Tool name 'docker_security_audit' and description 'Inspect containers for risky runtime settings without changing anything' explicitly indicate read-only inspection with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs docker_security_audit safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For docker_security_audit, this is the rule to start with:

docker_security_audit Allowed

docker_security_audit is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "docker_security_audit": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every docker_security_audit call is checked against it from then on.

FAQ

Questions about docker_security_audit

What does the docker_security_audit tool do? +

Inspect containers for risky runtime settings without changing anything. It is categorised as a Read tool in the Mcp Control Plane MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on docker_security_audit? +

Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for docker_security_audit: 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 Control Plane. Nothing to install.

What risk level is docker_security_audit? +

docker_security_audit is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit docker_security_audit? +

Yes. Add a rate_limit block to the docker_security_audit 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.

How do I block docker_security_audit completely? +

Set action: deny in the PolicyLayer policy for docker_security_audit. 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.

What MCP server provides docker_security_audit? +

docker_security_audit is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Control Plane, and thousands of servers like it.

This server

All 286 Mcp Control Plane tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →