AI agents call gitlab_list_users 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.
Listing users is a query operation that retrieves data with no side effects. It does not create, modify, delete, or execute any operations. While it may expose user identities, in the context of a GitLab instance where a user already has access to list users, the risk is low. The severity is low because misuse would only result in information disclosure rather than system compromise or data loss.
From the tool's definition Tool name is 'gitlab_list_users' and description states 'List GitLab users' - this is a read-only operation that retrieves user information without modifying, deleting, or executing any actions.
Documented attack patterns abuse exactly the kind of access gitlab_list_users gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GitLab MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for gitlab_list_users:
{
"version": "1",
"default": "deny",
"tools": {
"gitlab_list_users": {}
}
}gitlab_list_users is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List GitLab users. 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 gitlab_list_users: 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.
gitlab_list_users 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_users 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_users. 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_users is provided by the GitLab MCP Server MCP server (rifqi96/mcp-gitlab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GitLab MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
42 GitLab MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.