resolve_merge_request_discussion

WHAT IT DOES

What resolve_merge_request_discussion does on Kepler MCP GitLab Server

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

WHY IT NEEDS A POLICY

Why resolve_merge_request_discussion needs a policy

Resolving a merge request discussion changes its state in GitLab, which is a reversible modification operation (discussions can be unresolvedif needed). This is not a Read operation (it modifies state), not Destructive (it doesn't delete data), and not Execute (it's not running arbitrary code).

From the tool's definition Tool name 'resolve_merge_request_discussion' indicates modification of merge request discussion state. Sibling tools on the server include 'approve_merge_request', 'add_merge_request_comment', and 'create_merge_request', all of which are Write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resolve_merge_request_discussion Rate-limited

resolve_merge_request_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_merge_request_discussion": {
      "limits": [
        {
          "counter": "resolve_merge_request_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 Kepler MCP GitLab Server, so you can run agents against it safely.

FAQ

Questions about resolve_merge_request_discussion

What does the resolve_merge_request_discussion tool do? +

resolve_merge_request_discussion. It is categorised as a Write tool in the Kepler MCP GitLab Server 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_merge_request_discussion? +

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

What risk level is resolve_merge_request_discussion? +

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

Can I rate-limit resolve_merge_request_discussion? +

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

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

resolve_merge_request_discussion is provided by the Kepler MCP GitLab Server MCP server (ryan-rbw/kepler-mcp-gitlab-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.