AI agents call get_merge_request_analytics to retrieve information from Gitlab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and 'analytics' suffix indicate this retrieves or queries existing merge request metrics and statistics without modifying data. Confidence is slightly reduced (0.85 rather than higher) because the tool description is empty, but the server's stated purpose and naming convention strongly suggest read-only data retrieval. No evidence of side effects, code execution, or data modification.
From the tool's definition Tool name 'get_merge_request_analytics' indicates retrieval of merge request data. Server description states it 'provides tools for...analyzing merge request lifetimes' and supports 'reading repository code'.
Attacks that exploit this kind of access
get_merge_request_analytics. 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 get_merge_request_analytics: 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.
get_merge_request_analytics 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_merge_request_analytics 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_merge_request_analytics. 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_merge_request_analytics is provided by the Gitlab MCP server (kopiloto/mcp-gitlab-server). 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 →