close_epic · Mcp Gitlab MCP: Risk & Policy

WHAT IT DOES

What close_epic does on Mcp Gitlab

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

Closing an epic modifies project metadata reversibly—the epic state changes but can be reopened. This is a Write operation, not Destructive, since the action is reversible. Severity is medium due to potential workflow disruption if an agent closes critical epics without proper authorization, though the dry-run default provides a safety mechanism.

From the tool's definition Tool name 'close_epic' and description 'Fermer un epic' (Close an epic) indicates modification of epic state. Description specifies dry_run parameter with default true, requiring explicit dry_run=false to commit changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

close_epic Rate-limited

close_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": {
    "close_epic": {
      "limits": [
        {
          "counter": "close_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 close_epic

What does the close_epic tool do? +

Fermer un epic. Par defaut dry_run=true : retourne un apercu sans fermer. Passer dry_run=false apres confirmation. 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 close_epic? +

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

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

Can I rate-limit close_epic? +

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

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

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