contract-testing_admin_remove_role_from_user
Remove a single role from a user (admin). Parameters: - userId (string) *required*: UUID of the user - roleId (string) *required*: UUID of the role
This record as markdown: /tools/smartbear-mcp/contract-testing-admin-remove-role-from-user.md
What contract-testing_admin_remove_role_from_user does on SmartBear MCP
AI agents call contract-testing_admin_remove_role_from_user to permanently remove resources in SmartBear MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
roleId | string | Yes | UUID of the role |
userId | string | Yes | UUID of the user |
Parameters from the server's own tool schema.
Why contract-testing_admin_remove_role_from_user is rated Critical
Removing a role from a user is an irreversible administrative action that revokes access permissions. While a role could theoretically be re-added, role removal is an access control change that falls under destructive category due to its security implications and the fact that it removes/deletes an association.
From the tool's definition Remove a single role from a user (admin)
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs contract-testing_admin_remove_role_from_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_remove_role_from_user, this is the rule to start with:
contract-testing_admin_remove_role_from_user is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every contract-testing_admin_remove_role_from_user call is checked against it from then on.
Questions about contract-testing_admin_remove_role_from_user
Remove a single role from a user (admin). Parameters: - userId (string) *required*: UUID of the user - roleId (string) *required*: UUID of the role. It is categorised as a Destructive tool in the SmartBear MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
contract-testing_admin_remove_role_from_user accepts 2 parameters: roleId, userId. Required: roleId, 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_remove_role_from_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_remove_role_from_user is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the contract-testing_admin_remove_role_from_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_remove_role_from_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_remove_role_from_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.
Across the catalogue