update_incident · ServiceNow MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_incident does on ServiceNow MCP Server

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

This tool modifies existing incident records reversibly (updates rather than deletes), placing it squarely in the Write category. Severity is high because incidents track critical issues affecting business operations; unauthorized updates could misdirect incident handling, suppress escalations, or mask serious problems. Confidence is high due to explicit 'Update' language and clear operational context.

From the tool's definition Tool name 'update_incident' and description 'Update an existing incident in ServiceNow' indicate modification of existing data records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

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_incident

What does the update_incident tool do? +

Update an existing incident in ServiceNow. 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_incident? +

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