servicenow_update_record · Servicenow MCP: Risk & Policy

WHAT IT DOES

What servicenow_update_record does on Servicenow

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

This tool modifies existing records in ServiceNow (incidents, changes, problems, etc.) but does not delete or destroy data—changes can be reverted by updating fields again. The blast radius is medium: an AI agent could maliciously modify critical incident details, change request fields, or user records, impacting operations and data integrity, but the effect is not permanent or catastrophic like deletion.

From the tool's definition Tool description states 'Update fields on an existing ServiceNow record' and uses PATCH method with 'only specified fields are changed', indicating reversible modification of data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

servicenow_update_record Rate-limited

servicenow_update_record 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_record": {
      "limits": [
        {
          "counter": "servicenow_update_record_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_record

What does the servicenow_update_record tool do? +

Update fields on an existing ServiceNow record by sys_id (PATCH — only specified fields are changed). Args: - table (string): Table name - sys_id (string): 32-character sys_id of the record to update - data (object): Fields to update with their new values - response_format: Output format Returns: The updated record Examples: - Close a problem → table=. 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_record? +

Register the Servicenow MCP server in PolicyLayer and add a rule for servicenow_update_record: 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_record? +

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

Can I rate-limit servicenow_update_record? +

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

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

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