gitlab_list_groups
List GitLab groups and subgroups you have access to.
This record as markdown: /tools/dkeeno-gitlab-mcp-server/gitlab-list-groups.md
What gitlab_list_groups does on Gitlab
AI agents call gitlab_list_groups to retrieve information from Gitlab without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why gitlab_list_groups is rated Low
This tool retrieves and queries existing GitLab group data. It performs no modifications, deletions, or external operations. The action is read-only enumeration of accessible organizational units, which is a low-severity information disclosure with minimal blast radius.
From the tool's definition Tool name 'gitlab_list_groups' and description 'List GitLab groups and subgroups you have access to' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs gitlab_list_groups safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gitlab_list_groups, this is the rule to start with:
gitlab_list_groups is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab, apply this rule, and every gitlab_list_groups call is checked against it from then on.
Questions about gitlab_list_groups
List GitLab groups and subgroups you have access to. 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 gitlab_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. Nothing to install.
gitlab_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 gitlab_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 gitlab_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.
gitlab_list_groups is provided by the Gitlab MCP server (dkeeno/gitlab-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gitlab, and thousands of servers like it.
This server
Across the catalogue