set_current_update_set
Set an update set as the current active update set
This record as markdown: /tools/io-github-jschuller-mcp-server-servicenow/set-current-update-set.md
What set_current_update_set does on ServiceNow MCP Server
AI agents use set_current_update_set to create or update resources in ServiceNow MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow MCP Server environment.
Why set_current_update_set is rated Medium
This tool modifies application state by changing which update set is active. In ServiceNow, the 'current' update set determines the scope for subsequent changes and deployments.
From the tool's definition set_current_update_set: 'Set an update set as the current active update set' — this changes the active/current state of an update set, a reversible configuration change in ServiceNow
Attacks that exploit this kind of access
The rule that runs set_current_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 set_current_update_set, this is the rule to start with:
set_current_update_set stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 set_current_update_set call is checked against it from then on.
Questions about set_current_update_set
Set an update set as the current active update set. It is categorised as a Write tool in the ServiceNow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for set_current_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.
set_current_update_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_current_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 set_current_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.
set_current_update_set is provided by the ServiceNow MCP Server MCP server (pypi:mcp-server-servicenow). 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.
This server
Across the catalogue