add_issue_to_epic · Mcp Gitlab MCP: Risk & Policy

WHAT IT DOES

What add_issue_to_epic does on Mcp Gitlab

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

This tool creates or modifies associations between GitLab entities (issues and epics) but does not delete, execute arbitrary code, or move money. It is a reversible write operation. Severity is medium because misuse could create unwanted issue-epic associations affecting project organization and visibility, but the default dry-run mode provides safety and the operation is easily reversible.

From the tool's definition Tool description states 'Link an issue to an epic' which modifies the relationship between issues and epics. This is a reversible data modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_issue_to_epic Rate-limited

add_issue_to_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": {
    "add_issue_to_epic": {
      "limits": [
        {
          "counter": "add_issue_to_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 add_issue_to_epic

What does the add_issue_to_epic tool do? +

Link an issue to an epic. dry_run=true by default. Requires project_id and issue_iid (not the global issue ID). 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 add_issue_to_epic? +

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

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

Can I rate-limit add_issue_to_epic? +

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

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

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