Remove a Docker network
AI agents call remove_network to permanently remove resources in Docker MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a Docker network is an irreversible action that deletes network configuration and can disconnect containers. While not as critical as data deletion, it represents a destructive operation that severs infrastructure connections. High severity due to potential service disruption and inability to undo the action, though impact is scoped to a single network rather than system-wide or financial implications.
From the tool's definition Tool name 'remove_network' combined with description 'Remove a Docker network' indicates irreversible deletion of a network resource. The verb 'remove' in Docker's context is a destructive operation that cannot be undone without recreation.
Attacks that exploit this kind of access
Remove a Docker network. It is categorised as a Destructive tool in the Docker MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Docker MCP Server MCP server in PolicyLayer and add a rule for remove_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.
remove_network is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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.
Set action: deny in the PolicyLayer policy for remove_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.
remove_network is provided by the Docker MCP Server MCP server (pnmice/mcp-server-docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →