Critical Risk →

delete-todo

Delete a todo

How to control delete-todo ↓

AI agents call delete-todo to permanently remove resources in Todo List MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Deletion of data is irreversible and represents the most severe category applicable. Although the blast radius is limited to individual todo items rather than a full database wipe, the destructive nature and inability to undo the operation justifies 'high' severity. Confidence is high because the intent is explicit and unambiguous.

From the tool's definition Tool name 'delete-todo' with description 'Delete a todo' indicates irreversible removal of data. The action cannot be undone and permanently removes a todo item from the system.

Documented attack patterns abuse exactly the kind of access delete-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 delete-todo:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-todo"
  ]
}

delete-todo disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Todo List MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the delete-todo tool do? +

Delete a todo. It is categorised as a Destructive tool in the Todo List MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete-todo? +

Register the Todo List MCP Server MCP server in PolicyLayer and add a rule for delete-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.

What risk level is delete-todo? +

delete-todo is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete-todo? +

Yes. Add a rate_limit block to the delete-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.

How do I block delete-todo completely? +

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

What MCP server provides delete-todo? +

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

Enforce policy on every Todo List MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.