contract-testing_admin_set_user_roles

Replace all roles assigned to a user (admin). Parameters: - userId (string) *required*: UUID of the user - roles (array) *required*: Array of role UUIDs to assign

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/contract-testing-admin-set-user-roles.md

WHAT IT DOES

What contract-testing_admin_set_user_roles does on SmartBear MCP

AI agents use contract-testing_admin_set_user_roles 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
`roles`	array	Yes	Array of role UUIDs to assign
`userId`	string	Yes	UUID of the user

Parameters from the server's own tool schema.

RISK

Why contract-testing_admin_set_user_roles is rated Medium

This tool creates or modifies user access control settings by replacing role assignments. While it does not delete data irreversibly or move money, it has high blast radius because an AI agent misusing it could grant unauthorized admin privileges to arbitrary users, escalating permissions broadly across the system.

From the tool's definition Tool description states 'Replace all roles assigned to a user (admin)' — this modifies user permissions/roles, which is a reversible write operation. Parameters accept userId and roles array for assignment.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

contract-testing_admin_set_user_roles Rate-limited

contract-testing_admin_set_user_roles 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": {
    "contract-testing_admin_set_user_roles": {
      "limits": [
        {
          "counter": "contract-testing_admin_set_user_roles_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 SmartBear MCP, apply this rule, and every contract-testing_admin_set_user_roles call is checked against it from then on.

FAQ

Questions about contract-testing_admin_set_user_roles

What does the contract-testing_admin_set_user_roles tool do? +

Replace all roles assigned to a user (admin). Parameters: - userId (string) *required*: UUID of the user - roles (array) *required*: Array of role UUIDs to assign. 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.

What parameters does contract-testing_admin_set_user_roles accept? +

contract-testing_admin_set_user_roles accepts 2 parameters: roles, userId. Required: roles, userId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on contract-testing_admin_set_user_roles? +

Register the SmartBear MCP server in PolicyLayer and add a rule for contract-testing_admin_set_user_roles: 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.

What risk level is contract-testing_admin_set_user_roles? +

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

Can I rate-limit contract-testing_admin_set_user_roles? +

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

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

contract-testing_admin_set_user_roles 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.

KEEP EXPLORING

More on SmartBear, and thousands of servers like it.

This server

All 240 SmartBear tools →

Across the catalogue

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

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