resolve_discussion_thread · Qodev Gitlab MCP: Risk & Policy

WHAT IT DOES

What resolve_discussion_thread does on Qodev Gitlab

AI agents use resolve_discussion_thread 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 resolve_discussion_thread needs a policy

Resolving a discussion thread modifies data (thread state) reversibly, qualifying it as Write rather than Destructive. The lack of description lowers confidence slightly. Medium severity reflects that incorrect use could suppress important discussions, but the change is undoable.

From the tool's definition Tool name 'resolve_discussion_thread' indicates marking a discussion as resolved. In GitLab, resolving discussion threads is a reversible state change that modifies thread metadata without deleting content. No description provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resolve_discussion_thread Rate-limited

resolve_discussion_thread 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_discussion_thread": {
      "limits": [
        {
          "counter": "resolve_discussion_thread_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 resolve_discussion_thread

What does the resolve_discussion_thread tool do? +

resolve_discussion_thread. 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 resolve_discussion_thread? +

Register the Qodev Gitlab MCP server in PolicyLayer and add a rule for resolve_discussion_thread: 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 resolve_discussion_thread? +

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

Can I rate-limit resolve_discussion_thread? +

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

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

resolve_discussion_thread 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.