Set a merge request to merge when pipeline succeeds (auto-merge)
AI agents use set_auto_merge to create or update resources in Gitlab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitlab environment.
This tool creates or modifies merge request configuration in a reversible manner (auto-merge can be cancelled, as evidenced by the sibling tool cancel_auto_merge). It does not execute arbitrary code, delete data irreversibly, or move funds.
From the tool's definition Tool description states it will "Set a merge request to merge when pipeline succeeds (auto-merge)", which modifies the state of a merge request by enabling automatic merging.
Documented attack patterns abuse exactly the kind of access set_auto_merge 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 set_auto_merge:
{
"version": "1",
"default": "deny",
"tools": {
"set_auto_merge": {
"limits": [
{
"counter": "set_auto_merge_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_auto_merge stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set a merge request to merge when pipeline succeeds (auto-merge). It is categorised as a Write tool in the Gitlab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gitlab MCP server in PolicyLayer and add a rule for set_auto_merge: 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.
set_auto_merge is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_auto_merge 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 set_auto_merge. 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.
set_auto_merge is provided by the Gitlab MCP server (yoda-digital/mcp-gitlab-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 88 Gitlab tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
88 Gitlab tools catalogued and risk-classified — across an index of 42,500+ MCP servers.