create_epic · Mcp Gitlab MCP: Risk & Policy

WHAT IT DOES

What create_epic does on Mcp Gitlab

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

This tool creates new data (epics) in GitLab, which is a Write operation. It is not Destructive because epics can be undone/deleted. It is not Financial, Execute, or Read. The blast radius is medium: an agent could create many unwanted epics, polluting the project, but the impact is reversible. The dry-run-by-default safety mechanism is a mitigating factor but does not change the core classification.

From the tool's definition Tool creates a new epic in a GitLab group. Description states 'Creer un nouvel epic' (create a new epic). The dry-run mechanism (dry_run parameter) confirms this is a reversible write operation—epics can be deleted or modified after creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_epic Rate-limited

create_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": {
    "create_epic": {
      "limits": [
        {
          "counter": "create_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 create_epic

What does the create_epic tool do? +

Creer un nouvel epic dans un groupe GitLab. Par defaut dry_run=true : retourne un apercu sans creer. 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 create_epic? +

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

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

Can I rate-limit create_epic? +

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

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

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