schedule_delete
Delete one of your rig schedules by its schedule id (from schedule_list). The rig itself is untouched. Requires a logged-in identity.
This record as markdown: /tools/ai-rokha-rokha/schedule-delete.md
What schedule_delete does on Rokha
AI agents call schedule_delete to permanently remove resources in Rokha, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
schedule_id | string | Yes | UUID of the schedule to delete. |
Parameters from the server's own tool schema.
Why schedule_delete is rated Critical
Irreversibly deletes a schedule entry; cannot be undone.
From the tool's definition Delete one of your rig schedules by its schedule id
Attacks that exploit this kind of access
The rule that runs schedule_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For schedule_delete, this is the rule to start with:
schedule_delete 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 Rokha, apply this rule, and every schedule_delete call is checked against it from then on.
Questions about schedule_delete
Delete one of your rig schedules by its schedule id (from schedule_list). The rig itself is untouched. Requires a logged-in identity. It is categorised as a Destructive tool in the Rokha MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
schedule_delete accepts 1 parameter: schedule_id. Required: schedule_id. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for schedule_delete: 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 Rokha. Nothing to install.
schedule_delete 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 schedule_delete 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 schedule_delete. 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.
schedule_delete is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rokha, and thousands of servers like it.
Across the catalogue