crow_delete_bot_schedule
Delete a recurring bot-cron schedule by its scheduleId (from crow_list_bot_schedules).
This record as markdown: /tools/kh0pper-crow/crow-delete-bot-schedule.md
What crow_delete_bot_schedule does on Crow
AI agents call crow_delete_bot_schedule to permanently remove resources in Crow, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why crow_delete_bot_schedule is rated Critical
Deletion of scheduled automation tasks is a destructive action that cannot be easily undone. An AI agent that mistakenly deletes critical bot schedules could disrupt project management workflows, break automated processes, and require manual recovery. This is more severe than Write (reversible modification) but not Financial or Execute (code execution).
From the tool's definition Tool explicitly performs 'Delete a recurring bot-cron schedule' which is an irreversible deletion operation. The function name contains 'delete' and the description confirms removal of a schedule by ID.
Attacks that exploit this kind of access
The rule that runs crow_delete_bot_schedule safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_delete_bot_schedule, this is the rule to start with:
crow_delete_bot_schedule is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_delete_bot_schedule call is checked against it from then on.
Questions about crow_delete_bot_schedule
Delete a recurring bot-cron schedule by its scheduleId (from crow_list_bot_schedules). It is categorised as a Destructive tool in the Crow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Crow MCP server in PolicyLayer and add a rule for crow_delete_bot_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 Crow. Nothing to install.
crow_delete_bot_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 crow_delete_bot_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 crow_delete_bot_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.
crow_delete_bot_schedule is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
Across the catalogue