AI agents use complete-todo to create or update resources in Todo List MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todo List MCP Server environment.
This tool modifies data (the completion status of a todo item) but does so reversibly—a completed todo can be reopened or its status changed back. It does not delete data (which would be Destructive) or execute arbitrary code (which would be Execute).
From the tool's definition Tool name 'complete-todo' and description 'Mark a todo as completed' indicate a state modification operation that changes a todo item's status from incomplete to completed.
Documented attack patterns abuse exactly the kind of access complete-todo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Todo List MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for complete-todo:
{
"version": "1",
"default": "deny",
"tools": {
"complete-todo": {
"limits": [
{
"counter": "complete-todo_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}complete-todo 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.
Free to start. No card required.
Mark a todo as completed. It is categorised as a Write tool in the Todo List MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todo List MCP Server MCP server in PolicyLayer and add a rule for complete-todo: 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 Todo List MCP Server. Nothing to install.
complete-todo is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the complete-todo 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.
Set action: deny in the PolicyLayer policy for complete-todo. 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.
complete-todo is provided by the Todo List MCP Server MCP server (regibyte/todo-list-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Todo List MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 Todo List MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.