update_record

Update an existing record in any ServiceNow table (requires WRITE_ENABLED=true). Pass dry_run=true to preview a before→after field diff without writing.

SERVERServiceNow MCP Server SOURCE@aartiq/servicenow-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity verified Pull the record →

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

WHAT IT DOES

What update_record does on ServiceNow MCP Server

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

RISK

Why update_record is rated Medium

This tool modifies existing data in ServiceNow tables, making it a Write action. Severity is high because updates can affect critical business data (tickets, configurations, user records) across any table in ServiceNow, with broad blast radius depending on what records are updated. The tool does not delete (would be Destructive) or execute arbitrary code (would be Execute), so Write is the appropriate category.

From the tool's definition Tool description explicitly states 'Update an existing record in any ServiceNow table' and requires 'WRITE_ENABLED=true', clearly indicating data modification capability. The dry_run parameter confirms write semantics.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_record safely

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

update_record Rate-limited

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

FAQ

Questions about update_record

What does the update_record tool do? +

Update an existing record in any ServiceNow table (requires WRITE_ENABLED=true). Pass dry_run=true to preview a before→after field diff without writing. 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_record? +

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

What risk level is update_record? +

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

Can I rate-limit update_record? +

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

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

update_record is provided by the ServiceNow MCP Server MCP server (@aartiq/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 MCP Server, and thousands of servers like it.

This server

All 415 ServiceNow MCP Server tools →

Across the catalogue

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

Guides

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