This record as markdown: /tools/io-github-kivanccakmak-yaver/docker-rmi.md
What docker_rmi does on Yaver
AI agents call docker_rmi 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 | — | |
image | string | Yes |
Parameters from the server's own tool schema.
Why docker_rmi is rated Critical
docker_rmi removes Docker images, which is an irreversible operation. While not as immediately critical as deleting application data, removing images can disrupt deployment pipelines, CI/CD workflows, and development environments. In a local dev context (as Yaver is phone-first local dev), this could halt builds or deployments. The operation cannot be reversed without re-pulling or rebuilding the image.
From the tool's definition Tool name 'docker_rmi' and description 'Remove an image' indicate irreversible deletion of Docker images, a core destructive operation that cannot be undone without rebuilding.
Attacks that exploit this kind of access
The rule that runs docker_rmi 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_rmi, this is the rule to start with:
docker_rmi 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_rmi call is checked against it from then on.
Questions about docker_rmi
Remove an image. 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_rmi accepts 2 parameters: force, image. Required: image. 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_rmi: 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_rmi 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_rmi 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_rmi. 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_rmi 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