update_apply
Apply previously downloaded system updates. This is a DESTRUCTIVE operation that may reboot the system. The
This record as markdown: /tools/nasbridge/update-apply.md
What update_apply does on Nasbridge
AI agents call update_apply 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 update_apply is rated Critical
Applying system updates modifies core OS components irreversibly and can reboot the system, causing downtime. The description explicitly labels it as DESTRUCTIVE. This has a critical blast radius as it affects the entire TrueNAS system availability and integrity.
From the tool's definition 'Apply previously downloaded system updates. This is a DESTRUCTIVE operation that may reboot the system.'
Attacks that exploit this kind of access
The rule that runs update_apply 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 update_apply, this is the rule to start with:
update_apply 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 update_apply call is checked against it from then on.
Questions about update_apply
Apply previously downloaded system updates. This is a DESTRUCTIVE operation that may reboot the system. 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 update_apply: 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.
update_apply 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 update_apply 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 update_apply. 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.
update_apply 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