approve_merge_request · GitLab Code Review MCP

WHAT IT DOES

What approve_merge_request does on GitLab Code Review MCP

AI agents use approve_merge_request to create or update resources in GitLab Code Review MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitLab Code Review MCP environment.

WHY IT NEEDS A POLICY

Why approve_merge_request needs a policy

Approving a merge request is a reversible modification of code review state that can enable code deployment. While not destructive or financial, it modifies critical CI/CD workflow metadata and could allow unsafe code to merge if misused by an AI agent. This is Write-category (modifies data reversibly) rather than Execute, with high severity due to potential impact on production code quality and security.

From the tool's definition Tool name 'approve_merge_request' combined with sibling tools that manage 'approvals' and the server's stated capability to manage 'approvals through the GitLab API'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

approve_merge_request Rate-limited

approve_merge_request 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "approve_merge_request": {
      "limits": [
        {
          "counter": "approve_merge_request_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GitLab Code Review MCP, so you can run agents against it safely.

FAQ

Questions about approve_merge_request

What does the approve_merge_request tool do? +

approve_merge_request. It is categorised as a Write tool in the GitLab Code Review MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on approve_merge_request? +

Register the GitLab Code Review MCP server in PolicyLayer and add a rule for approve_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 Code Review MCP. Nothing to install.

What risk level is approve_merge_request? +

approve_merge_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit approve_merge_request? +

Yes. Add a rate_limit block to the approve_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.

How do I block approve_merge_request completely? +

Set action: deny in the PolicyLayer policy for approve_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.

What MCP server provides approve_merge_request? +

approve_merge_request is provided by the GitLab Code Review MCP server (lininn/gitlab-code-review-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.