switch_update_set
Switch the active Update Set context to a specified Update Set. [Scripting]
This record as markdown: /tools/servicenow-mcp-server/switch-update-set.md
What switch_update_set does on ServiceNow MCP Server
AI agents invoke switch_update_set to trigger actions in ServiceNow MCP Server. 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 switch_update_set is rated High
Switching the active Update Set context is an execution-level operation that changes the environment in which all subsequent configuration changes are tracked and deployed. Misuse could cause changes to be captured under the wrong Update Set, leading to incorrect deployments or loss of change tracking.
From the tool's definition 'Switch the active Update Set context to a specified Update Set' and '[Scripting]' tag
Attacks that exploit this kind of access
The rule that runs switch_update_set safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For switch_update_set, this is the rule to start with:
switch_update_set 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 ServiceNow MCP Server, apply this rule, and every switch_update_set call is checked against it from then on.
Questions about switch_update_set
Switch the active Update Set context to a specified Update Set. [Scripting]. It is categorised as a Execute tool in the ServiceNow MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for switch_update_set: 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 ServiceNow MCP Server. Nothing to install.
switch_update_set 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 switch_update_set 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 switch_update_set. 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.
switch_update_set is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow MCP Server, and thousands of servers like it.
Across the catalogue