Get current user information.
AI agents call get_current_user to retrieve information from GitLab MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user identity and profile information without modifying any data or triggering external actions. It is a straightforward query operation with no destructive or write capabilities. The blast radius is minimal—even if misused by an agent, it only exposes non-sensitive public user metadata.
From the tool's definition Tool name is 'get_current_user' and description states 'Get current user information.' The verb 'get' and the retrieval nature of the operation indicate data retrieval without side effects.
Attacks that exploit this kind of access
Get current user information. It is categorised as a Read tool in the GitLab MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for get_current_user: 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 MCP Server. Nothing to install.
get_current_user 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_current_user 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_current_user. 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_current_user is provided by the GitLab MCP Server MCP server (skmprb/gitlab-clone-mcp-server). 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 →