Retrieves a user based on their UID.
AI agents call get_user_by_uid to retrieve information from Rover MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query against the Red Hat internal groups API to fetch user information by unique identifier. There are no indications of data creation, modification, deletion, code execution, or financial operations. The blast radius of misuse is limited to unauthorized information access, which is typical of Read category tools.
From the tool's definition Tool description states it 'Retrieves a user based on their UID' - a pure query operation with no modification or side effects. The verb 'Retrieves' and the context of querying an internal groups API indicate data lookup functionality.
Attacks that exploit this kind of access
Retrieves a user based on their UID. It is categorised as a Read tool in the Rover MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rover MCP Server MCP server in PolicyLayer and add a rule for get_user_by_uid: 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 Rover MCP Server. Nothing to install.
get_user_by_uid 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 get_user_by_uid 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 get_user_by_uid. 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.
get_user_by_uid is provided by the Rover MCP Server MCP server (redhat-community-ai-tools/rover-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 →