Critical Risk →

boot_detach_disk

Detach a disk from the boot pool mirror. This is a DESTRUCTIVE operation — the

How to control boot_detach_disk ↓

What boot_detach_disk does on Truenas

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

Critical Risk

Why boot_detach_disk needs a policy

The tool explicitly labels itself as destructive and removes a disk from the boot pool mirror, which is an irreversible action that can compromise system boot capability. Misuse could render the system unbootable.

From the tool's definition Detach a disk from the boot pool mirror. This is a DESTRUCTIVE operation

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

How to control boot_detach_disk

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "boot_detach_disk"
  ]
}

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

  1. Create a free account and register Truenas — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about boot_detach_disk

What does the boot_detach_disk tool do? +

Detach a disk from the boot pool mirror. This is a DESTRUCTIVE operation — the. It is categorised as a Destructive tool in the Truenas 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 boot_detach_disk? +

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

What risk level is boot_detach_disk? +

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

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

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

boot_detach_disk is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Truenas tool call.

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

Free to start. No card required.

279 Truenas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.