mark_all_todos_done

Mark all pending GitLab to-do items as done for the current user

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-all-todos-done.md

WHAT IT DOES

What mark_all_todos_done does on Gitlab Mcp

AI agents use mark_all_todos_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_all_todos_done is rated Medium

This tool updates the status of to-do items from pending to done. This is a Write operation because it modifies data reversibly (the user can later unmark todos or the state can be reset). It is not Destructive because the to-do items themselves are not deleted or irreversibly removed.

From the tool's definition Tool description states 'Mark all pending GitLab to-do items as done' — this modifies the state of to-do items (marking them as done), which is a reversible write operation. The operation affects only the current user's to-do list, not system-wide data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mark_all_todos_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_all_todos_done, this is the rule to start with:

mark_all_todos_done Rate-limited

mark_all_todos_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_all_todos_done": {
      "limits": [
        {
          "counter": "mark_all_todos_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_all_todos_done call is checked against it from then on.

FAQ

Questions about mark_all_todos_done

What does the mark_all_todos_done tool do? +

Mark all pending GitLab to-do items as done for the current user. 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_all_todos_done? +

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

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

Can I rate-limit mark_all_todos_done? +

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

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

mark_all_todos_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 →