set_epic_iteration · Mcp Gitlab MCP: Risk & Policy

WHAT IT DOES

What set_epic_iteration does on Mcp Gitlab

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

This tool creates or modifies a relationship between an epic and an iteration, which is a reversible data change (the association can be removed or changed). It does not delete data, execute arbitrary code, or commit financial transactions. The 'dry_run=true by default' safety feature mitigates risk but does not change the underlying capability.

From the tool's definition 'Associate an iteration (sprint) with an epic' — modifies epic metadata by linking it to a sprint iteration. The description confirms it uses the Work Items API for data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_epic_iteration Rate-limited

set_epic_iteration 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": {
    "set_epic_iteration": {
      "limits": [
        {
          "counter": "set_epic_iteration_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 set_epic_iteration

What does the set_epic_iteration tool do? +

Associate an iteration (sprint) with an epic (uses Work Items API). 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 set_epic_iteration? +

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

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

Can I rate-limit set_epic_iteration? +

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

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

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