Merge an existing merge request.
AI agents invoke gitlab_merge_merge_request to trigger actions in Gitlab. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Merging a merge request is an irreversible operation that permanently integrates code into the target branch. While it is not purely 'destructive' (data isn't deleted), it cannot be trivially undone without a revert commit, and it triggers downstream effects (pipelines, deployments). This places it firmly in Execute with high severity, as a misuse could merge unreviewed or malicious code into production branches.
From the tool's definition "Merge an existing merge request" — merging integrates code changes into a target branch, triggering CI/CD pipelines and permanently altering branch history.
Documented attack patterns abuse exactly the kind of access gitlab_merge_merge_request gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gitlab, and nothing reaches the server without passing your rules. This is the rule we recommend for gitlab_merge_merge_request:
{
"version": "1",
"default": "deny",
"tools": {
"gitlab_merge_merge_request": {
"limits": [
{
"counter": "gitlab_merge_merge_request_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}gitlab_merge_merge_request stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Merge an existing merge request. It is categorised as a Execute tool in the Gitlab MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Gitlab MCP server in PolicyLayer and add a rule for gitlab_merge_merge_request: 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.
gitlab_merge_merge_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the gitlab_merge_merge_request 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_merge_merge_request. 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_merge_merge_request is provided by the Gitlab MCP server (mcpland/gitlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gitlab, 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.
190 Gitlab tools catalogued and risk-classified — across an index of 43,000+ MCP servers.