container_remove

THE RISK

Critical Risk

Why container_remove needs a policy

Removing a container is a destructive action that cannot be undone without recreating the container from scratch. This action permanently deletes the container and any unsaved data within it. Although the underlying image may remain, the container instance itself is irrevocably deleted.

From the tool's definition Tool name 'container_remove' and description 'Remove a container' directly indicate irreversible deletion of Docker container resources.

Documented attack patterns abuse exactly the kind of access container_remove gives an agent:

POLICY

How to control container_remove

PolicyLayer is an MCP gateway — it sits between your AI agents and ChatGPT MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for container_remove:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "container_remove"
  ]
}

container_remove disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register ChatGPT MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More ChatGPT MCP Server tools

Execute container_exec Execute a command in a running container Execute container_start Start a stopped container Execute container_stop Stop a running container Execute container_create Create and start a new Docker container Read container_logs Get container logs Read containers_list List all Docker containers

All 7 ChatGPT MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in ChatGPT MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about container_remove

What does the container_remove tool do? +

Remove a container. It is categorised as a Destructive tool in the ChatGPT MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on container_remove? +

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

What risk level is container_remove? +

container_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit container_remove? +

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

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

container_remove is provided by the ChatGPT MCP Server MCP server (toowiredd/chatgpt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ChatGPT MCP Server tool call.

Start from ChatGPT MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →