update_user

Update a user account (requires WRITE_ENABLED=true)

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-user.md

WHAT IT DOES

What update_user does on ServiceNow MCP Server

AI agents use update_user 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_user is rated Medium

This tool creates or modifies user account data in a reversible manner (user properties can be updated again). It is not destructive (accounts are not deleted), does not execute arbitrary code, and does not move money.

From the tool's definition Tool name is 'update_user' and description states 'Update a user account' — modifies user data. Description explicitly requires 'WRITE_ENABLED=true', confirming write intent.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_user 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_user, this is the rule to start with:

update_user Rate-limited

update_user 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_user": {
      "limits": [
        {
          "counter": "update_user_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_user call is checked against it from then on.

FAQ

Questions about update_user

What does the update_user tool do? +

Update a user account (requires WRITE_ENABLED=true). 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_user? +

Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for update_user: 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_user? +

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

Can I rate-limit update_user? +

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

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

update_user 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 365 ServiceNow MCP Server 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 →