user_update
Update an existing user account. All fields are optional — only provide the ones you want to change.
This record as markdown: /tools/nasbridge/user-update.md
What user_update does on Nasbridge
AI agents use user_update to create or update resources in Nasbridge, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nasbridge environment.
Why user_update is rated Medium
This tool creates or modifies user account data reversibly. While it could affect system access if credentials or permissions are changed, the modification is not permanent destruction and can be undone by updating the account again. The blast radius is constrained to a single user account unless the account modified is critical (e.g., administrator), hence 'medium' severity.
From the tool's definition Tool name 'user_update' and description 'Update an existing user account. All fields are optional — only provide the ones you want to change.' directly indicates modification of user account data.
Attacks that exploit this kind of access
The rule that runs user_update safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For user_update, this is the rule to start with:
user_update 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 Nasbridge, apply this rule, and every user_update call is checked against it from then on.
Questions about user_update
Update an existing user account. All fields are optional — only provide the ones you want to change. It is categorised as a Write tool in the Nasbridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nasbridge MCP server in PolicyLayer and add a rule for user_update: 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 Nasbridge. Nothing to install.
user_update 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 user_update 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 user_update. 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.
user_update is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
This server
Across the catalogue