network_rollback_changes
Rollback all pending (uncommitted) network interface changes, restoring the previous network configuration.
This record as markdown: /tools/nasbridge/network-rollback-changes.md
What network_rollback_changes does on Nasbridge
AI agents call network_rollback_changes 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 network_rollback_changes is rated Critical
Rolling back network configuration changes is irreversible in the sense that all pending uncommitted changes are discarded/overwritten. This cannot be undone — once rolled back, the pending changes are lost. Misuse by an AI agent could disrupt network connectivity on a TrueNAS instance, causing high-impact outages.
From the tool's definition Rollback all pending (uncommitted) network interface changes, restoring the previous network configuration
Attacks that exploit this kind of access
The rule that runs network_rollback_changes 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 network_rollback_changes, this is the rule to start with:
network_rollback_changes 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 network_rollback_changes call is checked against it from then on.
Questions about network_rollback_changes
Rollback all pending (uncommitted) network interface changes, restoring the previous network configuration. 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 network_rollback_changes: 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.
network_rollback_changes 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 network_rollback_changes 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 network_rollback_changes. 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.
network_rollback_changes 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