servicenow_update_incident · Servicenow MCP: Risk & Policy

WHAT IT DOES

What servicenow_update_incident does on Servicenow

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

WHY IT NEEDS A POLICY

Why servicenow_update_incident needs a policy

This tool modifies existing incident records in ServiceNow, making it a Write operation rather than Read (no retrieval only), Execute (no code/script execution), Destructive (updates are reversible, not deletions), or Financial.

From the tool's definition Tool name 'servicenow_update_incident' and description 'Update a ServiceNow incident' indicate modification of existing incident data. The verb 'update' is characteristic of reversible write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Servicenow, so you can run agents against it safely.

FAQ

Questions about servicenow_update_incident

What does the servicenow_update_incident tool do? +

Update a ServiceNow incident. It is categorised as a Write tool in the Servicenow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on servicenow_update_incident? +

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