complete_update_set · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

What complete_update_set does on ServiceNow-MCP

AI agents use complete_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 complete_update_set needs a policy

This tool changes the status of an Update Set from incomplete to complete, which is a Write operation—it modifies data reversibly. While the action could have downstream consequences if the Update Set is subsequently migrated to production, the tool itself only performs a state change, not migration or deletion.

From the tool's definition Tool name 'complete_update_set' and description 'Mark an Update Set as complete (ready for migration)' indicates a state transition that modifies an Update Set object.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

complete_update_set Rate-limited

complete_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": {
    "complete_update_set": {
      "limits": [
        {
          "counter": "complete_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 complete_update_set

What does the complete_update_set tool do? +

Mark an Update Set as complete (ready for migration). [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 complete_update_set? +

Register the ServiceNow- MCP server in PolicyLayer and add a rule for complete_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 complete_update_set? +

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

Can I rate-limit complete_update_set? +

Yes. Add a rate_limit block to the complete_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 complete_update_set completely? +

Set action: deny in the PolicyLayer policy for complete_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 complete_update_set? +

complete_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.