删除待办事项（通过将其标记为已取消）。需要提供待办事项ID和授权令牌。
AI agents call delete_todo to permanently remove resources in Things MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although the implementation marks items as 'cancelled' rather than permanently erasing records, from a user perspective this irreversibly removes the todo from active use. The action cannot be undone through normal tool usage (no restore/undelete tool listed), making it destructive. While less severe than data corruption, unauthorized deletion of todos could impact task management and productivity.
From the tool's definition Tool name 'delete_todo' and description states it deletes a todo item (by marking it as cancelled). The description explicitly uses language indicating removal: '删除待办事项' (delete/remove todo item).
Attacks that exploit this kind of access
删除待办事项（通过将其标记为已取消）。需要提供待办事项ID和授权令牌。. It is categorised as a Destructive tool in the Things MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Things 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 Things 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 Things MCP Server MCP server (mieluoxxx/things_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 →