schedule_create
Schedule a SAVED rig to run on a recurring cadence — from every minute up to weekly (those three presets only). Every fire is owner-scoped and draws on the owner's daily run budget (a spent budget skips the fire, recorded as skipped_budget). The rig must be SAVED first (rig_author) — pass its UUI...
This record as markdown: /tools/ai-rokha-rokha/schedule-create.md
What schedule_create does on Rokha
AI agents use schedule_create to create or update resources in Rokha, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rokha environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
rig_id | string | Yes | UUID of the SAVED rig to run on schedule. |
cadence | string | Yes | How often the rig runs. 1 minute is the fastest preset; every fire is budget-gated. |
rig_name | string | — | Optional display name for the schedule. |
Parameters from the server's own tool schema.
Why schedule_create is rated Medium
Creates a recurring schedule entry; reversible by deleting the schedule, draws on budget.
From the tool's definition Schedule a SAVED rig to run on a recurring cadence
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs schedule_create 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_create, this is the rule to start with:
schedule_create stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every schedule_create call is checked against it from then on.
Questions about schedule_create
Schedule a SAVED rig to run on a recurring cadence — from every minute up to weekly (those three presets only). Every fire is owner-scoped and draws on the owner's daily run budget (a spent budget skips the fire, recorded as skipped_budget). The rig must be SAVED first (rig_author) — pass its UUID as rig_id. Requires a logged-in identity (Authorization: Bearer <JWT>). Cap: 20 schedules per account. It is categorised as a Write tool in the Rokha MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
schedule_create accepts 3 parameters: rig_id, cadence, rig_name. Required: rig_id, cadence. 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_create: 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_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the schedule_create 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_create. 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_create 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.
This server
Across the catalogue