Remove a todo item from the list. Use this when the user wants to delete a task. Provide the todo ID.
AI agents call remove_todo to permanently remove resources in db4app Todo MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes todo items from the database. Deletion is irreversible and cannot be undone—once a todo is removed, it is gone. While the blast radius is limited to a single todo list (not system-wide data), the irreversible nature of the operation and the potential for an AI agent to delete important tasks without proper confirmation places this in the Destructive category.
From the tool's definition Tool name 'remove_todo' and description 'Remove a todo item from the list' and 'delete a task' indicate irreversible deletion of data records.
Attacks that exploit this kind of access
Remove a todo item from the list. Use this when the user wants to delete a task. Provide the todo ID. It is categorised as a Destructive tool in the db4app Todo MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the db4app Todo MCP Server MCP server in PolicyLayer and add a rule for remove_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 db4app Todo MCP Server. Nothing to install.
remove_todo 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 remove_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 remove_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.
remove_todo is provided by the db4app Todo MCP Server MCP server (maxabrahamsson/todo-mcp-db4app). 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 →