snow_workflow_transition
⚠️ LEGACY: Manage workflow transitions (deprecated - ServiceNow recommends Flow Designer). Actions: create, update, delete, list
This record as markdown: /tools/serac/snow-workflow-transition.md
What snow_workflow_transition does on Serac
AI agents call snow_workflow_transition 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_workflow_transition is rated Critical
The tool supports delete actions on workflow transitions, which can irreversibly remove workflow logic in a production ServiceNow environment. Deletion of workflow transitions is not easily reversible and could break running workflows. The most severe applicable category is Destructive due to the delete action.
From the tool's definition Actions: create, update, delete, list — includes delete action; operates on workflow transitions in ServiceNow
Attacks that exploit this kind of access
The rule that runs snow_workflow_transition 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_workflow_transition, this is the rule to start with:
snow_workflow_transition 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_workflow_transition call is checked against it from then on.
Questions about snow_workflow_transition
⚠️ LEGACY: Manage workflow transitions (deprecated - ServiceNow recommends Flow Designer). Actions: create, update, delete, list. 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_workflow_transition: 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_workflow_transition 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_workflow_transition 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_workflow_transition. 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_workflow_transition 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