contract-testing_admin_update_user
Update a user's profile or active status (admin). Parameters: - userId (string) *required*: UUID of the user to update - active (boolean): Whether the user is active - email (string): New email address - firstName (string): First name - lastName (string): Last name - name (string): Display name
This record as markdown: /tools/smartbear-mcp/contract-testing-admin-update-user.md
What contract-testing_admin_update_user does on SmartBear MCP
AI agents use contract-testing_admin_update_user to create or update resources in SmartBear MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SmartBear MCP environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Display name |
email | string | — | New email address |
active | boolean | — | Whether the user is active |
userId | string | Yes | UUID of the user to update |
lastName | string | — | Last name |
firstName | string | — | First name |
Parameters from the server's own tool schema.
Why contract-testing_admin_update_user is rated Medium
This tool creates or modifies user data reversibly. It can change email addresses, names, and active status—all Write operations. The 'admin' designation and ability to deactivate users elevates severity to high because unauthorized use could lock out legitimate users or compromise accounts, but changes are theoretically reversible (user can be reactivated, email changed back).
From the tool's definition Tool name includes 'update' and description states 'Update a user's profile or active status (admin)'. Parameters include modifiable fields: email, firstName, lastName, name, and active status.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs contract-testing_admin_update_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SmartBear MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For contract-testing_admin_update_user, this is the rule to start with:
contract-testing_admin_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 SmartBear MCP, apply this rule, and every contract-testing_admin_update_user call is checked against it from then on.
Questions about contract-testing_admin_update_user
Update a user's profile or active status (admin). Parameters: - userId (string) *required*: UUID of the user to update - active (boolean): Whether the user is active - email (string): New email address - firstName (string): First name - lastName (string): Last name - name (string): Display name. It is categorised as a Write tool in the SmartBear MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
contract-testing_admin_update_user accepts 6 parameters: name, email, active, userId, lastName, firstName. Required: userId. The full parameter table on this page comes from the server's own tool schema.
Register the SmartBear MCP server in PolicyLayer and add a rule for contract-testing_admin_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 SmartBear MCP. Nothing to install.
contract-testing_admin_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 contract-testing_admin_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 contract-testing_admin_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.
contract-testing_admin_update_user is provided by the SmartBear MCP server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SmartBear, and thousands of servers like it.
This server
Across the catalogue