mark_todo_done

Mark a GitLab to-do item as done

SERVERGitlab Mcp SOURCE@zereight/mcp-gitlab

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-zereight-gitlab-mcp/mark-todo-done.md

WHAT IT DOES

What mark_todo_done does on Gitlab Mcp

AI agents use mark_todo_done to create or update resources in Gitlab Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitlab Mcp environment.

RISK

Why mark_todo_done is rated Medium

This tool modifies an existing to-do item's status from pending to done, which is a reversible write operation. The blast radius is minimal—it only affects a single user's to-do list item and can be undone by marking it undone again. This does not delete data, execute external code, or create financial obligations.

From the tool's definition Tool name 'mark_todo_done' and description 'Mark a GitLab to-do item as done' indicate a state change operation on a to-do item.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mark_todo_done safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mark_todo_done, this is the rule to start with:

mark_todo_done Rate-limited

mark_todo_done 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": {
    "mark_todo_done": {
      "limits": [
        {
          "counter": "mark_todo_done_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every mark_todo_done call is checked against it from then on.

FAQ

Questions about mark_todo_done

What does the mark_todo_done tool do? +

Mark a GitLab to-do item as done. It is categorised as a Write tool in the Gitlab Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mark_todo_done? +

Register the Gitlab MCP server in PolicyLayer and add a rule for mark_todo_done: 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 Gitlab Mcp. Nothing to install.

What risk level is mark_todo_done? +

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

Can I rate-limit mark_todo_done? +

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

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

mark_todo_done is provided by the Gitlab MCP server (@zereight/mcp-gitlab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gitlab, and thousands of servers like it.

This server

All 215 Gitlab tools →

Across the catalogue

sms_mark_read on Twilio SMS MCP Server →mark-as-read on Meme MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →