AI agents call get_user_info to retrieve information from Gitlab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about the authenticated user without modifying, executing, or deleting anything. It is a simple information lookup operation. Severity is low because user profile information is typically non-sensitive operational metadata, and the blast radius of misuse (e.g., an AI learning user details) is minimal compared to other categories.
From the tool's definition Tool name 'get_user_info' and description 'Get information about the authenticated user' indicate a retrieval operation with no side effects. The verb 'Get' and context of querying user information align with read-only functionality.
Attacks that exploit this kind of access
Get information about the authenticated user. It is categorised as a Read tool in the Gitlab MCP Server, which means it retrieves data without modifying state.
Register the Gitlab MCP server in PolicyLayer and add a rule for get_user_info: 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 Gitlab. Nothing to install.
get_user_info 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_info 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_info. 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_info is provided by the Gitlab MCP server (kopiloto/mcp-gitlab-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_user_info is one line of Gitlab's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →