connect_docker · ContainerGuard MCP: Risk & Policy

WHAT IT DOES

What connect_docker does on ContainerGuard MCP

AI agents invoke connect_docker to trigger actions in ContainerGuard MCP. 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 IT NEEDS A POLICY

Why connect_docker needs a policy

Establishing a connection to a remote Docker daemon initiates an active network session and enables subsequent control over containerized workloads. While a connection itself is not purely destructive or financial, it is an active operation that triggers external system interaction (the remote Docker API), enabling privileged container management.

From the tool's definition 连接到远程Docker守护进程 (Connect to remote Docker daemon)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_docker Rate-limited

connect_docker 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "connect_docker": {
      "limits": [
        {
          "counter": "connect_docker_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ContainerGuard MCP, so you can run agents against it safely.

FAQ

Questions about connect_docker

What does the connect_docker tool do? +

连接到远程Docker守护进程. It is categorised as a Execute tool in the ContainerGuard MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on connect_docker? +

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

What risk level is connect_docker? +

connect_docker is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit connect_docker? +

Yes. Add a rate_limit block to the connect_docker 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 connect_docker completely? +

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

connect_docker is provided by the ContainerGuard MCP server (rockmelodies/containerguardmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.