Get roles assigned to a specific user or group.
AI agents call GetUserRoles to retrieve information from Veeam VBR v13 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that queries user or group role assignments. It retrieves information about permissions/roles already assigned but does not create, modify, delete, or execute any operations. The blast radius of misuse is low—an agent obtaining role information could inform reconnaissance but cannot directly change system state or cause destructive outcomes. It belongs in the Read category.
From the tool's definition Tool name 'GetUserRoles' and description 'Get roles assigned to a specific user or group' indicate a query operation that retrieves existing role assignment data without modification or side effects.
Attacks that exploit this kind of access
Get roles assigned to a specific user or group. It is categorised as a Read tool in the Veeam VBR v13 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Veeam VBR v13 MCP Server MCP server in PolicyLayer and add a rule for GetUserRoles: 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.
GetUserRoles is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the GetUserRoles 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 GetUserRoles. 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.
GetUserRoles 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 →