update_issue · GitLab MCP: Risk & Policy

WHAT IT DOES

What update_issue does on GitLab MCP

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

WHY IT NEEDS A POLICY

Why update_issue needs a policy

The tool creates or modifies data reversibly, fitting the Write category. An AI agent misusing this could close/reopen issues inappropriately, spam state changes, or disrupt project workflows, but changes are reversible. Severity is medium because the blast radius is scoped to a single issue's metadata and state, affecting project tracking but not causing permanent data loss or triggering financial operations.

From the tool's definition Tool name is 'update_issue' and description states 'Update an issue' with capability to change state via state_event parameter. This modifies issue data reversibly (close/reopen are state transitions, not deletions).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_issue Rate-limited

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

FAQ

Questions about update_issue

What does the update_issue tool do? +

Update an issue. Use state_event = "close" or "reopen" to change state. It is categorised as a Write tool in the GitLab MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_issue? +

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

What risk level is update_issue? +

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

Can I rate-limit update_issue? +

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

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

update_issue is provided by the GitLab MCP server (shahabmosavi/gitlab_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.