AI agents call gitlab_get_project 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.
The tool retrieves project metadata/details without modifying, executing, or deleting anything. It is a pure read operation that queries existing data. Severity is low because project details are typically not sensitive enough to cause significant harm if exposed to an AI agent, though it does provide information that could inform further actions.
From the tool's definition Tool name is 'gitlab_get_project' and description states 'Get details of a specific GitLab project' — this is a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access gitlab_get_project 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_get_project:
{
"version": "1",
"default": "deny",
"tools": {
"gitlab_get_project": {}
}
}gitlab_get_project 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.
Get details of a specific GitLab project. 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_get_project: 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_get_project 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_get_project 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_get_project. 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_get_project 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.