删除定时任务（软删除）
AI agents call cron_remove to permanently remove resources in MCP Cron Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although marked as soft delete, removing a scheduled task is a destructive action that eliminates a job configuration and halts its execution. The task cannot be automatically recovered through normal tool operations; recovery would require administrative intervention or backup restoration. This irreversibility and the loss of scheduled job continuity places it in the Destructive category.
From the tool's definition Tool name 'cron_remove' combined with description '删除定时任务（软删除）' which translates to 'Delete scheduled task (soft delete)'. The term '删除' (delete) and 'remove' indicate irreversible removal of cron job configurations, even if implemented as soft delete.
Attacks that exploit this kind of access
删除定时任务（软删除）. It is categorised as a Destructive tool in the MCP Cron Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Cron Server MCP server in PolicyLayer and add a rule for cron_remove: 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 Cron Server. Nothing to install.
cron_remove 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 cron_remove 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 cron_remove. 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.
cron_remove is provided by the MCP Cron Server MCP server (nolan57/opencode-mcp-cron). 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 →