connect_network · Docker MCP Server MCP: Risk & Policy

WHAT IT DOES

What connect_network does on Docker MCP Server

AI agents use connect_network to create or update resources in Docker MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docker MCP Server environment.

WHY IT NEEDS A POLICY

Why connect_network needs a policy

Connecting a container to a network is a write operation that modifies container configuration reversibly (it can be undone via disconnect_network, which is listed as a sibling tool). While it affects system state, the blast radius is contained to network routing and connectivity for that container, and the operation is not destructive, financial, or a direct code execution.

From the tool's definition The tool description states it 'Connect[s] a container to a network', which modifies the network configuration of a container. This is a reversible change that alters the state of a container's network connectivity without deleting data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_network Rate-limited

connect_network stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_network": {
      "limits": [
        {
          "counter": "connect_network_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about connect_network

What does the connect_network tool do? +

Connect a container to a network. It is categorised as a Write tool in the Docker MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on connect_network? +

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

What risk level is connect_network? +

connect_network is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit connect_network? +

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

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

connect_network is provided by the Docker MCP Server MCP server (swartdraak/docker-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.