update_epic_note · Mcp Gitlab MCP: Risk & Policy

WHAT IT DOES

What update_epic_note does on Mcp Gitlab

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

update_epic_note modifies existing data (epic notes) in a reversible manner. This is a Write operation rather than Read (it changes state), Destructive (edits are reversible), or Execute (no code/command execution). The default dry-run mode provides safety but the tool's purpose is data modification.

From the tool's definition Tool description states 'Edit the body of an existing epic note' — a reversible modification operation. The 'dry_run=true by default' indicates safety mechanisms are in place but do not change the fundamental Write classification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_epic_note Rate-limited

update_epic_note 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": {
    "update_epic_note": {
      "limits": [
        {
          "counter": "update_epic_note_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 update_epic_note

What does the update_epic_note tool do? +

Edit the body of an existing epic note. Get note_id from list_epic_notes. 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 update_epic_note? +

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

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

Can I rate-limit update_epic_note? +

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

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

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