AI agents call get_project_merge_requests to retrieve information from GitLab MCP for Code Review without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix indicates a query/retrieval operation that fetches existing merge request data without modifying or deleting anything. The sibling tools establish a clear pattern where 'fetch'/'get' operations retrieve data from GitLab. Even though the description is empty, the naming convention and context from other tools on the server strongly suggest this is a read operation with no side effects.
From the tool's definition Tool name 'get_project_merge_requests' uses the 'get' verb, which retrieves data. Based on sibling tools like 'fetch_merge_request' and 'fetch_merge_request_diff' that explicitly retrieve merge request data, this tool retrieves a list of merge requests from a…
Documented attack patterns abuse exactly the kind of access get_project_merge_requests gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GitLab MCP for Code Review, and nothing reaches the server without passing your rules. This is the rule we recommend for get_project_merge_requests:
{
"version": "1",
"default": "deny",
"tools": {
"get_project_merge_requests": {}
}
}get_project_merge_requests 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_project_merge_requests. It is categorised as a Read tool in the GitLab MCP for Code Review MCP Server, which means it retrieves data without modifying state.
Register the GitLab MCP for Code Review MCP server in PolicyLayer and add a rule for get_project_merge_requests: 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 for Code Review. Nothing to install.
get_project_merge_requests 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 get_project_merge_requests 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 get_project_merge_requests. 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.
get_project_merge_requests is provided by the GitLab MCP for Code Review MCP server (mehmetakinn/gitlab-mcp-code-review). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GitLab MCP for Code Review, 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.
8 GitLab MCP for Code Review tools catalogued and risk-classified — across an index of 43,000+ MCP servers.