snow_change_manage
Unified change management (create, update_state, approve, create_task, schedule_cab)
This record as markdown: /tools/serac/snow-change-manage.md
What snow_change_manage does on Serac
AI agents invoke snow_change_manage to trigger actions in Serac. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why snow_change_manage is rated High
This tool performs multiple operations in ServiceNow's change management system: creating change records, updating their state, approving changes, creating tasks, and scheduling CAB meetings. These are not simple writes — 'approve' and 'update_state' trigger downstream workflows and external operations (e.g., CAB scheduling, approval chains).
From the tool's definition Unified change management (create, update_state, approve, create_task, schedule_cab)
Attacks that exploit this kind of access
The rule that runs snow_change_manage 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_change_manage, this is the rule to start with:
snow_change_manage stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Serac, apply this rule, and every snow_change_manage call is checked against it from then on.
Questions about snow_change_manage
Unified change management (create, update_state, approve, create_task, schedule_cab). It is categorised as a Execute tool in the Serac MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Serac MCP server in PolicyLayer and add a rule for snow_change_manage: 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_change_manage is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the snow_change_manage 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_change_manage. 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_change_manage 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