todo_mark_done · MCP Todo Server MCP: Risk & Policy

WHAT IT DOES

What todo_mark_done does on MCP Todo Server

AI agents use todo_mark_done to create or update resources in MCP Todo Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Todo Server environment.

WHY IT NEEDS A POLICY

Why todo_mark_done needs a policy

This tool modifies existing data (changes a todo's completion status) but the change is reversible—the todo can be unmarked or re-opened. It does not delete data (which would be Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read). The impact is limited to task state management with low blast radius.

From the tool's definition Tool name 'todo_mark_done' and description 'Mark a todo as completed' indicate a state modification operation that updates a todo item's status to completed.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

todo_mark_done Rate-limited

todo_mark_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": {
    "todo_mark_done": {
      "limits": [
        {
          "counter": "todo_mark_done_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 Todo Server, so you can run agents against it safely.

FAQ

Questions about todo_mark_done

What does the todo_mark_done tool do? +

Mark a todo as completed. It is categorised as a Write tool in the MCP Todo Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on todo_mark_done? +

Register the MCP Todo Server MCP server in PolicyLayer and add a rule for todo_mark_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 MCP Todo Server. Nothing to install.

What risk level is todo_mark_done? +

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

Can I rate-limit todo_mark_done? +

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

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

todo_mark_done is provided by the MCP Todo Server MCP server (xenagarage/mcp-todo-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.