incident_update · ServiceNow MCP Server MCP: Risk & Policy

WHAT IT DOES

What incident_update does on ServiceNow MCP Server

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

incident_update performs a reversible modification (Write category) of incident data within ServiceNow. While updates are not destructive, they modify important operational records that may affect ticketing workflows, SLA tracking, and service continuity operations.

From the tool's definition Tool name: 'incident_update'; Description: 'Update an existing incident'. This modifies existing incident records in ServiceNow, which are typically business-critical operational records used for IT service management and incident tracking.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

incident_update Rate-limited

incident_update 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": {
    "incident_update": {
      "limits": [
        {
          "counter": "incident_update_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 incident_update

What does the incident_update tool do? +

Update an existing incident. 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 incident_update? +

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

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

Can I rate-limit incident_update? +

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

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

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