update_incident

Update fields on an existing incident (requires WRITE_ENABLED=true)

SERVERServiceNow-MCP SOURCEtedorigawa001/servicenow-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tedorigawa001-servicenow-mcp/update-incident.md

WHAT IT DOES

What update_incident does on ServiceNow-MCP

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

RISK

Why update_incident is rated Medium

This tool creates or modifies data reversibly by updating incident fields in ServiceNow. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely retrieve data (Read).

From the tool's definition Tool name 'update_incident' and description 'Update fields on an existing incident' indicate modification of existing data. The description explicitly notes a WRITE_ENABLED permission requirement, confirming write capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_incident safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_incident, this is the rule to start with:

update_incident Rate-limited

update_incident 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_incident": {
      "limits": [
        {
          "counter": "update_incident_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow-MCP, apply this rule, and every update_incident call is checked against it from then on.

FAQ

Questions about update_incident

What does the update_incident tool do? +

Update fields on an existing incident (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_incident? +

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

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

Can I rate-limit update_incident? +

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

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

update_incident 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.

KEEP EXPLORING

More on ServiceNow, and thousands of servers like it.

This server

All 495 ServiceNow tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →