system_reboot
Reboot the TrueNAS system. This is a DESTRUCTIVE operation — all running services will be interrupted. The
This record as markdown: /tools/nasbridge/system-reboot.md
What system_reboot does on Nasbridge
AI agents call system_reboot 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 system_reboot is rated Critical
A system reboot forcibly interrupts all running services and processes on the TrueNAS host. While the system will eventually come back online, the act of rebooting causes irreversible disruption to in-flight operations, active connections, and running jobs.
From the tool's definition Reboot the TrueNAS system. This is a DESTRUCTIVE operation — all running services will be interrupted.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs system_reboot 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 system_reboot, this is the rule to start with:
system_reboot 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 system_reboot call is checked against it from then on.
Questions about system_reboot
Reboot the TrueNAS system. This is a DESTRUCTIVE operation — all running services will be interrupted. 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 system_reboot: 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.
system_reboot 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 system_reboot 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 system_reboot. 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.
system_reboot 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