Clear all todos for a session
AI agents call todo_clear 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 permanently removes all todos at once, which is an irreversible data loss operation. It affects all items in a session simultaneously, creating a high blast radius if invoked by an AI agent without user confirmation. While not financial, it is more severe than Write (which is reversible) and qualifies as Destructive due to the inability to undo the operation.
From the tool's definition 'Clear all todos for a session' — the verb 'clear' combined with 'all' indicates irreversible deletion of all todo items in a session without granular filtering or recovery options.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all todos for a session. 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_clear: 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_clear 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_clear 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_clear. 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_clear 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 →