boot_attach_disk
Attach a disk to the boot pool to create or extend a mirror. This is a DESTRUCTIVE operation that will erase the target disk. The
This record as markdown: /tools/spranab-truenas-mcp/boot-attach-disk.md
What boot_attach_disk does on Truenas
AI agents call boot_attach_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.
Why boot_attach_disk is rated Critical
The tool explicitly states it is destructive and will erase the target disk. Erasing a disk is irreversible data loss. Attaching to the boot pool mirror also modifies critical system boot infrastructure, amplifying the blast radius to potentially unbootable systems.
From the tool's definition 'This is a DESTRUCTIVE operation that will erase the target disk'
Attacks that exploit this kind of access
The rule that runs boot_attach_disk safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Truenas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For boot_attach_disk, this is the rule to start with:
boot_attach_disk 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 Truenas, apply this rule, and every boot_attach_disk call is checked against it from then on.
Questions about boot_attach_disk
Attach a disk to the boot pool to create or extend a mirror. This is a DESTRUCTIVE operation that will erase the target disk. 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.
Register the Truenas MCP server in PolicyLayer and add a rule for boot_attach_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.
boot_attach_disk 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 boot_attach_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.
Set action: deny in the PolicyLayer policy for boot_attach_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.
boot_attach_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.
More on Truenas, and thousands of servers like it.
Across the catalogue