AI agents call compare_versions 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.
Based on naming convention and context from sibling tools on the GitLab MCP server, 'compare_versions' most likely retrieves diff or comparison data between two versions. No destructive, financial, or write operations are evident. The empty description prevents full certainty, but the tool name indicates a query/retrieval action rather than modification or execution.
From the tool's definition Tool name 'compare_versions' suggests a read operation that retrieves and compares data between versions without modifying state. Description is empty/uninformative, lowering confidence.
Documented attack patterns abuse exactly the kind of access compare_versions 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 compare_versions:
{
"version": "1",
"default": "deny",
"tools": {
"compare_versions": {}
}
}compare_versions 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.
compare_versions. 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 compare_versions: 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.
compare_versions 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 compare_versions 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 compare_versions. 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.
compare_versions 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.