Create a new update set in ServiceNow and optionally set it as the current update set.
AI agents use create_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.
An AI agent can call create_update_set faster than any human can review — one bad instruction and it creates or modifies resources in ServiceNow MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Create a new update set in ServiceNow and optionally set it as the current 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 create_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.
create_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 create_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 create_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.
create_update_set is provided by the ServiceNow MCP Server MCP server (windoze95/servicewow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.