update_change_request · ServiceNow MCP Server MCP

WHAT IT DOES

What update_change_request does on ServiceNow MCP Server

AI agents use update_change_request 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.

WHY IT NEEDS A POLICY

Why update_change_request needs a policy

This tool modifies ServiceNow change request records. While the modification is reversible (changes can be undone through subsequent updates), the blast radius is high because change requests often control critical infrastructure changes—an AI agent could maliciously or accidentally update approval statuses, schedules, or implementation details of production changes affecting system availability.

From the tool's definition Tool name is 'update_change_request' and description states 'Update an existing change request'. The verb 'update' indicates modification of existing data in a reversible manner without deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_change_request Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_change_request": {
      "limits": [
        {
          "counter": "update_change_request_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 Server, so you can run agents against it safely.

FAQ

Questions about update_change_request

What does the update_change_request tool do? +

Update an existing change request. 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.

How do I enforce a policy on update_change_request? +

Register the ServiceNow MCP Server 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 ServiceNow MCP Server. Nothing to install.

What risk level is update_change_request? +

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

Can I rate-limit update_change_request? +

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.

How do I block update_change_request completely? +

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.

What MCP server provides update_change_request? +

update_change_request is provided by the ServiceNow MCP Server MCP server (shameerampcome/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.