ensure_active_update_set · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why ensure_active_update_set needs a policy

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

Recommended rule Ready

Verdict

ensure_active_update_set Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ensure_active_update_set": {
      "limits": [
        {
          "counter": "ensure_active_update_set_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ServiceNow-MCP, so you can run agents against it safely.

FAQ

Questions about ensure_active_update_set

What does the ensure_active_update_set tool do? +

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.

How do I enforce a policy on ensure_active_update_set? +

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.

What risk level is ensure_active_update_set? +

ensure_active_update_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ensure_active_update_set? +

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.

How do I block ensure_active_update_set completely? +

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.

What MCP server provides ensure_active_update_set? +

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.