close_merge_request · Qodev Gitlab MCP: Risk & Policy

WHAT IT DOES

What close_merge_request does on Qodev Gitlab

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

WHY IT NEEDS A POLICY

Why close_merge_request needs a policy

Closing a merge request modifies its state reversibly (it can be reopened), so it falls under Write rather than Destructive. The impact is significant because an AI agent could inappropriately close critical merge requests needed for code integration, disrupting development workflows. This warrants 'high' severity due to potential workflow disruption, though not 'critical' since the action is reversible.

From the tool's definition Tool name 'close_merge_request' indicates it modifies the state of a merge request by closing it. Sibling tools like 'merge_merge_request', 'create_merge_request', and 'comment_on_merge_request' confirm this server manages merge request lifecycle operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

close_merge_request Rate-limited

close_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": {
    "close_merge_request": {
      "limits": [
        {
          "counter": "close_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 Qodev Gitlab, so you can run agents against it safely.

FAQ

Questions about close_merge_request

What does the close_merge_request tool do? +

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

How do I enforce a policy on close_merge_request? +

Register the Qodev Gitlab MCP server in PolicyLayer and add a rule for close_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 Qodev Gitlab. Nothing to install.

What risk level is close_merge_request? +

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

Can I rate-limit close_merge_request? +

Yes. Add a rate_limit block to the close_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 close_merge_request completely? +

Set action: deny in the PolicyLayer policy for close_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 close_merge_request? +

close_merge_request is provided by the Qodev Gitlab MCP server (qodevai/gitlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.