Updates one or more fields on an existing change request.
AI agents use update_change_request to create or update resources in Snow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Snow environment.
This tool modifies existing change request records (reversible operation), classifying it as Write. Severity is high because unauthorized changes to ITOM/ITSM change requests could disrupt critical infrastructure operations, affect compliance audit trails, or trigger unintended deployments. However, it is not Destructive since updates are reversible and do not permanently delete data.
From the tool's definition Tool name 'update_change_request' and description 'Updates one or more fields on an existing change request' indicate modification of existing data in ServiceNow's change management system.
Documented attack patterns abuse exactly the kind of access update_change_request gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Snow, and nothing reaches the server without passing your rules. This is the rule we recommend for update_change_request:
{
"version": "1",
"default": "deny",
"tools": {
"update_change_request": {
"limits": [
{
"counter": "update_change_request_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_change_request 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.
Free to start. No card required.
Updates one or more fields on an existing change request. It is categorised as a Write tool in the Snow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Snow MCP server in PolicyLayer and add a rule for update_change_request: 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 Snow. Nothing to install.
update_change_request 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 update_change_request 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 update_change_request. 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.
update_change_request is provided by the Snow MCP server (shunyaai/snow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Snow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
88 Snow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.