Edit roles assigned to a user or group.
AI agents use UpdateUserRoles to create or update resources in Veeam VBR v13 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Veeam VBR v13 MCP Server environment.
This tool modifies authentication and authorization metadata by editing role assignments. While reversible (making it Write rather than Destructive), it has high severity because role changes can grant or revoke access to critical backup/recovery functions across the Veeam infrastructure, affecting security posture and operational control.
From the tool's definition Tool name 'UpdateUserRoles' and description 'Edit roles assigned to a user or group' indicate modification of access control configuration. The verb 'Edit' explicitly signals a reversible write operation that changes user/group permissions.
Attacks that exploit this kind of access
Edit roles assigned to a user or group. It is categorised as a Write tool in the Veeam VBR v13 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Veeam VBR v13 MCP Server MCP server in PolicyLayer and add a rule for UpdateUserRoles: 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 Veeam VBR v13 MCP Server. Nothing to install.
UpdateUserRoles 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 UpdateUserRoles 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 UpdateUserRoles. 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.
UpdateUserRoles is provided by the Veeam VBR v13 MCP Server MCP server (kid-boy/veeam-mcp-13). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →