List groups visible to the authenticated user.
AI agents call list_groups to retrieve information from GitLab MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries group metadata accessible to the user but does not create, modify, delete, or execute any operations. It is a straightforward enumeration endpoint with no destructive or state-changing effects. Severity is low because exposure of group names and structures to an AI agent carries minimal risk; an attacker would need these groups to already exist and be visible to the authenticated user.
From the tool's definition Tool name is 'list_groups' and description states 'List groups visible to the authenticated user.' The verb 'list' and the action of retrieving/querying group information with no modification or side effects are characteristic of a Read operation.
Attacks that exploit this kind of access
List groups visible to the authenticated user. It is categorised as a Read tool in the GitLab MCP MCP Server, which means it retrieves data without modifying state.
Register the GitLab MCP server in PolicyLayer and add a rule for list_groups: 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.
list_groups 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 list_groups 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 list_groups. 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.
list_groups is provided by the GitLab MCP server (shahabmosavi/gitlab_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 →