whoami

Get current authenticated user details

SERVERGitlab Mcp SOURCE@zereight/mcp-gitlab

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-zereight-gitlab-mcp/whoami.md

WHAT IT DOES

What whoami does on Gitlab Mcp

AI agents call whoami to retrieve information from Gitlab Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why whoami is rated Low

This tool retrieves user identity information, which is a read-only operation with no side effects. The blast radius of misuse is minimal—an AI agent could only learn who the current user is, which is typically non-sensitive information in a GitLab context and often needed for proper operation.

From the tool's definition Tool name 'whoami' and description 'Get current authenticated user details' indicates a query operation that retrieves information about the authenticated user without modifying any state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs whoami safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For whoami, this is the rule to start with:

whoami Allowed

whoami is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "whoami": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every whoami call is checked against it from then on.

FAQ

Questions about whoami

What does the whoami tool do? +

Get current authenticated user details. It is categorised as a Read tool in the Gitlab Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on whoami? +

Register the Gitlab MCP server in PolicyLayer and add a rule for whoami: 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. Nothing to install.

What risk level is whoami? +

whoami is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit whoami? +

Yes. Add a rate_limit block to the whoami 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.

How do I block whoami completely? +

Set action: deny in the PolicyLayer policy for whoami. 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.

What MCP server provides whoami? +

whoami is provided by the Gitlab MCP server (@zereight/mcp-gitlab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gitlab, and thousands of servers like it.

This server

All 215 Gitlab tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →