일정을 삭제합니다.
AI agents call delete_todo to permanently remove resources in Mcp Todo — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes todos from the system without possibility of recovery. While the impact scope (single todo item) is bounded, the irreversible nature of deletion and potential for accidental/malicious bulk removal by an AI agent classifies this as Destructive. Severity is high rather than critical because damage is limited to individual task records, not system-wide infrastructure or financial data.
From the tool's definition Tool name is 'delete_todo' and description in Korean '일정을 삭제합니다' translates to 'Delete a task/schedule'. The sibling tools list confirms this server includes delete operations (delete_memo, delete_todo). Deletion is irreversible.
Attacks that exploit this kind of access
일정을 삭제합니다. It is categorised as a Destructive tool in the Mcp Todo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Todo 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 Mcp Todo. 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 Mcp Todo MCP server (moon-daeseung/mcp-todo). 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 →