ensure_active_update_set
Ensure an active Update Set exists; create one automatically if none is in progress. [Scripting]
This record as markdown: /tools/tedorigawa001-servicenow-mcp/ensure-active-update-set.md
What ensure_active_update_set does on ServiceNow-MCP
AI agents use ensure_active_update_set to create or update resources in ServiceNow-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow-MCP environment.
Why ensure_active_update_set is rated Medium
The tool creates a new Update Set record in ServiceNow if one does not already exist, which is a reversible data creation action (Write category). Severity is medium because creating an Update Set is a configuration change that could affect subsequent operations, but is not destructive and does not directly execute arbitrary code or move money.
From the tool's definition Tool description states 'create one automatically if none is in progress' — this modifies ServiceNow state by creating an Update Set record. The '[Scripting]' tag indicates it prepares the environment for scripted operations.
Attacks that exploit this kind of access
The rule that runs ensure_active_update_set safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ensure_active_update_set, this is the rule to start with:
ensure_active_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, apply this rule, and every ensure_active_update_set call is checked against it from then on.
Questions about ensure_active_update_set
Ensure an active Update Set exists; create one automatically if none is in progress. [Scripting]. It is categorised as a Write tool in the ServiceNow-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow MCP server in PolicyLayer and add a rule for ensure_active_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. Nothing to install.
ensure_active_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 ensure_active_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 ensure_active_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.
ensure_active_update_set is provided by the ServiceNow MCP server (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow, and thousands of servers like it.
This server
Across the catalogue