resolve_mr_discussion · Mcp Gitlab MCP: Risk & Policy

WHAT IT DOES

What resolve_mr_discussion does on Mcp Gitlab

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

WHY IT NEEDS A POLICY

Why resolve_mr_discussion needs a policy

This tool changes the resolution status of merge request discussions, which is a reversible modification of metadata. It does not delete data (not Destructive), execute arbitrary code (not Execute), or move money (not Financial).

From the tool's definition Tool description states it marks an MR discussion as 'resolved (or unresolved)', which modifies the state of discussion metadata. The default dry_run=true mitigates risk but the actual operation modifies data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resolve_mr_discussion Rate-limited

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

FAQ

Questions about resolve_mr_discussion

What does the resolve_mr_discussion tool do? +

Mark an MR discussion as resolved (or unresolved). dry_run=true by default. It is categorised as a Write tool in the Mcp 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 resolve_mr_discussion? +

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

What risk level is resolve_mr_discussion? +

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

Can I rate-limit resolve_mr_discussion? +

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

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

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

// THE FULL RECORD

resolve_mr_discussion is one line of Mcp Gitlab's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →