boot_detach_disk
Detach a disk from the boot pool mirror. This is a DESTRUCTIVE operation — the
This record as markdown: /tools/nasbridge/boot-detach-disk.md
What boot_detach_disk does on Nasbridge
AI agents call boot_detach_disk to permanently remove resources in Nasbridge, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why boot_detach_disk is rated Critical
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
Attacks that exploit this kind of access
The rule that runs boot_detach_disk safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For boot_detach_disk, this is the rule to start with:
boot_detach_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 Nasbridge, apply this rule, and every boot_detach_disk call is checked against it from then on.
Questions about boot_detach_disk
Detach a disk from the boot pool mirror. This is a DESTRUCTIVE operation — the. It is categorised as a Destructive tool in the Nasbridge MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nasbridge 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 Nasbridge. Nothing to install.
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.
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.
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.
boot_detach_disk is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
Across the catalogue