This record as markdown: /tools/io-github-kivanccakmak-yaver/docker-rm.md
What docker_rm does on Yaver
AI agents call docker_rm to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
force | boolean | — | |
container | string | Yes |
Parameters from the server's own tool schema.
Why docker_rm is rated Critical
Removing a Docker container is a destructive action that cannot be undone. Once removed, the container and its state are permanently deleted unless backed up separately. This cannot be reversed through normal means and represents an irreversible change to the system state, placing it in the Destructive category rather than Write (which requires reversibility).
From the tool's definition Tool name is 'docker_rm' and description states 'Remove a container.' The verb 'Remove' combined with the docker_rm command (the standard Docker CLI instruction to delete containers) indicates irreversible deletion of resources.
Attacks that exploit this kind of access
The rule that runs docker_rm safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For docker_rm, this is the rule to start with:
docker_rm is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every docker_rm call is checked against it from then on.
Questions about docker_rm
Remove a container. It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
docker_rm accepts 2 parameters: force, container. Required: container. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for docker_rm: 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 Yaver. Nothing to install.
docker_rm 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 docker_rm 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 docker_rm. 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.
docker_rm is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue