snow_rollback_deployment
Rollback failed deployment by reverting to previous version or deleting artifact
This record as markdown: /tools/serac/snow-rollback-deployment.md
What snow_rollback_deployment does on Serac
AI agents call snow_rollback_deployment to permanently remove resources in Serac, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why snow_rollback_deployment is rated Critical
Rolling back a deployment and deleting artifacts are irreversible actions that can overwrite or permanently remove production configurations and update sets in ServiceNow. The blast radius is critical as this could affect live enterprise systems.
From the tool's definition 'Rollback failed deployment by reverting to previous version or deleting artifact' — explicitly mentions deleting artifact and reverting deployments, both irreversible operations
Attacks that exploit this kind of access
The rule that runs snow_rollback_deployment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Serac, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snow_rollback_deployment, this is the rule to start with:
snow_rollback_deployment 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 Serac, apply this rule, and every snow_rollback_deployment call is checked against it from then on.
Questions about snow_rollback_deployment
Rollback failed deployment by reverting to previous version or deleting artifact. It is categorised as a Destructive tool in the Serac MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Serac MCP server in PolicyLayer and add a rule for snow_rollback_deployment: 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 Serac. Nothing to install.
snow_rollback_deployment 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 snow_rollback_deployment 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 snow_rollback_deployment. 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.
snow_rollback_deployment is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Serac, and thousands of servers like it.
Across the catalogue