删除定时任务
AI agents call delete_schedule to permanently remove resources in MCP Reminder Service — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes scheduled reminders without the ability to recover them. Once deleted, a scheduled task cannot be undone, making this a destructive operation. The high severity reflects that an AI agent could accidentally or maliciously remove important scheduled notifications, potentially disrupting user workflows and communication pipelines.
From the tool's definition Tool name 'delete_schedule' and Chinese description '删除定时任务' (delete scheduled task) directly indicates irreversible deletion of scheduled reminders/notifications.
Attacks that exploit this kind of access
删除定时任务. It is categorised as a Destructive tool in the MCP Reminder Service MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Reminder Service MCP server in PolicyLayer and add a rule for delete_schedule: 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 Reminder Service. Nothing to install.
delete_schedule 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_schedule 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_schedule. 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_schedule is provided by the MCP Reminder Service MCP server (xiaohui/mcp_reminder). 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 →