gitlab_merge_mr

What gitlab_merge_mr does on Gitlab

AI agents use gitlab_merge_mr 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.

Why gitlab_merge_mr is rated Medium

Merging a merge request modifies the target branch by incorporating new code, which is a reversible write operation. While the tool description is empty, the name and server context strongly indicate code integration capability. This could cause significant disruption if misused (e.g., merging untested or malicious code to production branches), but the change can be reverted, making it Write rather than Destructive.

From the tool's definition Tool name 'gitlab_merge_mr' indicates merging a merge request. The server description mentions 'merge requests' as part of GitLab DevOps automation. Merging MRs creates/modifies code in the repository and triggers CI/CD pipelines.

The rule that runs gitlab_merge_mr safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gitlab_merge_mr, this is the rule to start with:

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

Questions about gitlab_merge_mr