reopen_epic · Mcp Gitlab MCP: Risk & Policy

WHAT IT DOES

What reopen_epic does on Mcp Gitlab

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

Reopening an epic changes workflow state and may trigger notifications, reassignments, or pipeline updates, but is fully reversible. This is a Write operation (create/modify) rather than Read (no data retrieval), Destructive (state is not deleted), Execute (no arbitrary code), Financial (no monetary impact), or Other.

From the tool's definition Tool reopens a closed epic (reversible state change). Description states 'dry_run=true by default', indicating the tool modifies project management state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reopen_epic Rate-limited

reopen_epic 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": {
    "reopen_epic": {
      "limits": [
        {
          "counter": "reopen_epic_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 reopen_epic

What does the reopen_epic tool do? +

Reopen a closed epic. 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 reopen_epic? +

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

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

Can I rate-limit reopen_epic? +

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

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

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