servicenow_update_incident

Update fields on an existing ServiceNow incident — state, priority, assignment. Use sys_id from servicenow_get_incident.

SERVERLocal SOURCElocal-mcp

Medium RISK CLASS

Category Write

Parameters 71 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What servicenow_update_incident does on Local

AI agents use servicenow_update_incident to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.

Parameter	Type	Required	Description
`state`	string	—	1=New, 2=In Progress, 3=On Hold, 6=Resolved, 7=Closed
`sys_id`	string	Yes	Incident sys_id from servicenow_get_incident
`urgency`	string	—	1=Critical, 2=High, 3=Medium, 4=Low
`priority`	string	—	1=Critical, 2=High, 3=Moderate, 4=Low, 5=Planning
`assigned_to`	string	—	Username or email to assign to
`close_notes`	string	—	Resolution notes (required when state=6 or 7)
`short_description`	string	—	Updated summary

Parameters from the server's own tool schema.

RISK

Why servicenow_update_incident is rated Medium

The tool modifies existing data (incident state, priority, assignment) but does not permanently delete or destroy records. Updates are reversible through subsequent modifications.

From the tool's definition Tool name contains 'update' and description states 'Update fields on an existing ServiceNow incident — state, priority, assignment.' These are reversible modifications to incident records.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs servicenow_update_incident safely

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

servicenow_update_incident Rate-limited

servicenow_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": {
    "servicenow_update_incident": {
      "limits": [
        {
          "counter": "servicenow_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 Local, apply this rule, and every servicenow_update_incident call is checked against it from then on.

FAQ

Questions about servicenow_update_incident

What does the servicenow_update_incident tool do? +

Update fields on an existing ServiceNow incident — state, priority, assignment. Use sys_id from servicenow_get_incident. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does servicenow_update_incident accept? +

servicenow_update_incident accepts 7 parameters: state, sys_id, urgency, priority, assigned_to, close_notes, short_description. Required: sys_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on servicenow_update_incident? +

Register the Local MCP server in PolicyLayer and add a rule for servicenow_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 Local. Nothing to install.

What risk level is servicenow_update_incident? +

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

Can I rate-limit servicenow_update_incident? +

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

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

servicenow_update_incident is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local 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 →