cleanup_stale_containers

THE RISK

Critical Risk

Why cleanup_stale_containers needs a policy

Cleaning up stale containers involves removing Docker containers that are no longer in active use. This is an irreversible action: once a container is deleted, its writable layer and any non-persisted state are permanently gone. The 'fix conflicts' aspect may also involve forcibly removing conflicting resources.

From the tool's definition 'Clean up stale containers and fix conflicts' — removing/deleting containers is irreversible; container state and data may be permanently lost

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

POLICY

How to control cleanup_stale_containers

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

policy.json

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

cleanup_stale_containers 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 TrueNAS Scale 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 TrueNAS Scale MCP Server tools

Destructive delete_custom_app Delete a Custom App and optionally its data volumes Execute bulk_app_operation Start/stop multiple apps at once Execute deploy_custom_app Deploy a new Custom App from Docker Compose configuration Execute start_custom_app Start a stopped Custom App Execute stop_custom_app Stop a running Custom App Write update_custom_app Update an existing Custom App with new Docker Compose configuration Read diagnose_docker_issues Diagnose Docker engine issues and network conflicts Read get_app_logs Retrieve logs from a Custom App

All 13 TrueNAS Scale 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 TrueNAS Scale 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 cleanup_stale_containers

What does the cleanup_stale_containers tool do? +

Clean up stale containers and fix conflicts. It is categorised as a Destructive tool in the TrueNAS Scale 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 cleanup_stale_containers? +

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

What risk level is cleanup_stale_containers? +

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

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

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

cleanup_stale_containers is provided by the TrueNAS Scale MCP Server MCP server (svnstfns/truenas-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 TrueNAS Scale MCP Server tool call.

Start from TrueNAS Scale 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 →