bootenv_delete
Delete a boot environment. This is a DESTRUCTIVE operation — the
This record as markdown: /tools/nasbridge/bootenv-delete.md
What bootenv_delete does on Nasbridge
AI agents call bootenv_delete 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 bootenv_delete is rated Critical
The tool deletes a boot environment, which is a critical system component. Boot environments cannot be easily recovered once deleted, and removing the wrong one could render a TrueNAS system unbootable. This is irreversible data/system state loss with extreme blast radius if an AI agent targets the wrong boot environment. Severity is critical due to potential system unavailability.
From the tool's definition Tool name is 'bootenv_delete' and description explicitly states 'This is a DESTRUCTIVE operation' followed by an em-dash indicating irreversible deletion of a boot environment.
Attacks that exploit this kind of access
The rule that runs bootenv_delete 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 bootenv_delete, this is the rule to start with:
bootenv_delete 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 bootenv_delete call is checked against it from then on.
Questions about bootenv_delete
Delete a boot environment. 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 bootenv_delete: 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.
bootenv_delete 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 bootenv_delete 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 bootenv_delete. 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.
bootenv_delete 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