disconnect_network · Docker MCP Server MCP: Risk & Policy

WHAT IT DOES

What disconnect_network does on Docker MCP Server

AI agents use disconnect_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 disconnect_network needs a policy

This tool modifies container network configuration by removing a network connection, which is a Write operation—it changes state but is reversible (can reconnect). It's not Destructive because the network and container persist and the action can be undone.

From the tool's definition Tool name 'disconnect_network' and description 'Disconnect a container from a network' indicate a network configuration modification. This changes container network bindings but is reversible through reconnection.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disconnect_network Rate-limited

disconnect_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": {
    "disconnect_network": {
      "limits": [
        {
          "counter": "disconnect_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 disconnect_network

What does the disconnect_network tool do? +

Disconnect a container from 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 disconnect_network? +

Register the Docker MCP Server MCP server in PolicyLayer and add a rule for disconnect_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 disconnect_network? +

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

Can I rate-limit disconnect_network? +

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

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

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