Retrieve a specific user role.\r\n\r\n\r\n<h4>Required permission(s):</h4><span class=
AI agents call retrieve_userroles to retrieve information from Wpm Mcp Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns user role data without creating, modifying, deleting, or executing operations. It has minimal blast radius if misused by an AI agent—exposure of role information is a confidentiality concern but not destructive or operationally dangerous. Low severity is appropriate for information disclosure of this type.
From the tool's definition Tool name is 'retrieve_userroles' with description indicating it retrieves a specific user role. The verb 'retrieve' and the absence of any modification, deletion, or execution language indicate a read-only operation. No side effects are mentioned.
Attacks that exploit this kind of access
Retrieve a specific user role.\r\n\r\n\r\n<h4>Required permission(s):</h4><span class=. It is categorised as a Read tool in the Wpm Mcp Server MCP Server, which means it retrieves data without modifying state.
Register the Wpm Mcp Server MCP server in PolicyLayer and add a rule for retrieve_userroles: 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 Wpm Mcp Server. Nothing to install.
retrieve_userroles 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 retrieve_userroles 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 retrieve_userroles. 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.
retrieve_userroles is provided by the Wpm Mcp Server MCP server (wpm-mcp-server-mcp). 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 →