unapprove_merge_request

What unapprove_merge_request does on Gitlab Mcp

AI agents use unapprove_merge_request to create or update resources in Gitlab Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitlab Mcp environment.

Why unapprove_merge_request is rated Medium

This tool changes metadata state on a merge request (approval status) without permanently deleting data or executing arbitrary code. It is reversible—an approval can be re-added. This makes it a Write operation rather than Destructive. Severity is medium because misuse could delay or disrupt code review workflows, but the impact is contained to a single merge request's approval status and can be readily remedied.

From the tool's definition The tool 'unapprove_merge_request' modifies the approval state of a merge request by removing an approval, as stated in the description 'Unapprove a merge request'. This is a reversible state change operation.

The rule that runs unapprove_merge_request safely

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

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

Questions about unapprove_merge_request