update_user
Update a user account (requires WRITE_ENABLED=true)
This record as markdown: /tools/tedorigawa001-servicenow-mcp/update-user.md
What update_user does on ServiceNow-MCP
AI agents use update_user to create or update resources in ServiceNow-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow-MCP environment.
Why update_user is rated Medium
This tool creates or modifies user account data in ServiceNow. It is reversible (user attributes can be changed again) and has no permanent deletion or financial implications. The blast radius is medium because modifying user accounts could affect system access, permissions, or authentication, but the impact is bounded to a single user record unless an agent systematically modifies many accounts.
From the tool's definition Tool name is 'update_user' and description states 'Update a user account'. The description explicitly notes a requirement flag 'WRITE_ENABLED=true', confirming this modifies data.
Attacks that exploit this kind of access
The rule that runs update_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, 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 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.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow-MCP, apply this rule, and every update_user call is checked against it from then on.
Questions about update_user
Update a user account (requires WRITE_ENABLED=true). It is categorised as a Write tool in the ServiceNow-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow 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. Nothing to install.
update_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
update_user is provided by the ServiceNow MCP server (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow, and thousands of servers like it.
This server
Across the catalogue