remove_container

Remove a Docker container

SERVERNcp SOURCE@portel/ncp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-portel-dev-ncp/remove-container.md

WHAT IT DOES

What remove_container does on Ncp

AI agents call remove_container to permanently remove resources in Ncp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why remove_container is rated Critical

Removing a Docker container destroys the container and cannot be undone without restoring from backups. This is a destructive operation with potential blast radius if applied to production containers, causing service disruption and data loss if volumes are not properly managed. This exceeds Write (reversible modification) and qualifies as Destructive.

From the tool's definition Tool name 'remove_container' combined with description 'Remove a Docker container' indicates irreversible deletion of a container and its associated state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_container safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_container, this is the rule to start with:

remove_container Hidden

remove_container is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every remove_container call is checked against it from then on.

FAQ

Questions about remove_container

What does the remove_container tool do? +

Remove a Docker container. It is categorised as a Destructive tool in the Ncp 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 remove_container? +

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

What risk level is remove_container? +

remove_container 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 remove_container? +

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

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

remove_container is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ncp, and thousands of servers like it.

This server

All 275 Ncp tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →