close_issue · Qodev Gitlab MCP: Risk & Policy

WHAT IT DOES

What close_issue does on Qodev Gitlab

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

Closing an issue modifies state but is not destructive—it can be undone by reopening. It does not delete data, execute arbitrary code, or move money. While the description is empty (lowering confidence slightly), the tool name and context clearly indicate a Write operation that changes issue status in a way that affects project workflow and visibility.

From the tool's definition Tool name 'close_issue' indicates a state-change operation on GitLab issues. Sibling tools like 'create_issue' and 'comment_on_issue' confirm this is a data-modification interface. Closing an issue is reversible (issues can be reopened).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

close_issue Rate-limited

close_issue 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_issue": {
      "limits": [
        {
          "counter": "close_issue_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_issue

What does the close_issue tool do? +

close_issue. 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_issue? +

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

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

Can I rate-limit close_issue? +

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

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

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