Delete a Zen (todo) item.
AI agents call happy_zen_delete_todo to permanently remove resources in Happy Server MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a todo item without the ability to undo the action. Deletion is irreversible and constitutes a destructive operation. While the blast radius is limited to individual todo items (not system-critical), the permanent loss of data warrants 'high' severity. An AI agent with access could inadvertently or maliciously delete important task records.
From the tool's definition Tool name is 'happy_zen_delete_todo' with description 'Delete a Zen (todo) item.' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a Zen (todo) item. It is categorised as a Destructive tool in the Happy Server MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Happy Server MCP server in PolicyLayer and add a rule for happy_zen_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 Happy Server MCP. Nothing to install.
happy_zen_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 happy_zen_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 happy_zen_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.
happy_zen_delete_todo is provided by the Happy Server MCP server (zhigang1992/happy-server-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 →