Remove a todo by ID
AI agents call todo_remove to permanently remove resources in MCP Todo Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool deletes a todo item by ID, which is an irreversible operation that cannot be undone. Even though individual todo items are typically low-value data, the tool performs a destructive action (permanent deletion) rather than a reversible write.
From the tool's definition Tool name 'todo_remove' combined with description 'Remove a todo by ID' indicates irreversible deletion of data. The verb 'remove' in the context of data management typically means permanent deletion.
Attacks that exploit this kind of access
Remove a todo by ID. It is categorised as a Destructive tool in the MCP Todo Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Todo Server MCP server in PolicyLayer and add a rule for todo_remove: 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.
todo_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the todo_remove 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 todo_remove. 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.
todo_remove 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →