update_change_request · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

What update_change_request does on ServiceNow-MCP

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

This tool creates or modifies change request data in ServiceNow without deleting it (reversible Write operation). Severity is high because change requests often control production deployments and infrastructure changes; misconfiguration could impact operational workflows, approvals, and compliance tracking, though the effect depends on which fields are modified and by what values an AI agent supplies.

From the tool's definition Tool name: 'update_change_request'. Description: 'Update fields on a change request (requires WRITE_ENABLED=true)'. The verb 'Update' and the explicit WRITE_ENABLED flag confirm this modifies data reversibly.

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, so you can run agents against it safely.

FAQ

Questions about update_change_request

What does the update_change_request tool do? +

Update fields on a change request (requires WRITE_ENABLED=true). 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 update_change_request? +

Register the ServiceNow- 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. 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 (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.