Delete a todo from the calendar.
AI agents call delete_todo to permanently remove resources in CalDAV MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes todo entries without the ability to undo the operation. While the blast radius is somewhat limited to calendar data (not system-critical), the irreversible nature of deletion and potential for loss of important task records justifies the Destructive category and high severity. Confidence is high because the intent is unambiguous from both name and description.
From the tool's definition Tool name 'delete_todo' combined with description 'Delete a todo from the calendar' indicates irreversible deletion of calendar data.
Attacks that exploit this kind of access
Delete a todo from the calendar. It is categorised as a Destructive tool in the CalDAV MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CalDAV 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 CalDAV MCP Server. Nothing to install.
delete_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 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.
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.
delete_todo is provided by the CalDAV MCP Server MCP server (thegreatgooo/radicale-mcp). 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 →