Create a routine that fires an ops verb on a target machine on a schedule. Pick exactly one of run_at (one-shot), cron (recurring), or repeat_interval (every N minutes). Machine can be 'local' (this agent), 'primary' (the user's primary device alias), or any peer deviceId — peer routing uses the ...
AI agents use routine_create to create or update resources in Yaver — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
cron | string | — | 5-field cron expression for recurring runs (minute hour day month weekday), e.g. '0 9 * * 1-5' for weekdays at 9am UTC. Use this OR run_at OR repeat_interval. |
name | string | — | Human-readable label. Optional; defaults to 'routine: <verb>'. |
verb | string | Yes | Registered ops verb name (e.g. 'run', 'build', 'workspace'). |
run_at | string | — | ISO8601 UTC timestamp for one-shot run, e.g. 2026-05-05T06:00:00Z. Use this OR cron OR repeat_interval, never more than one. |
machine | string | — | 'local', 'primary', 'auto', or a deviceId. Defaults to 'local'. |
payload | object | — | Verb-specific JSON payload. Shape depends on the chosen verb (see ops_verbs). |
max_runs | integer | — | Stop after this many fires (0 = unlimited). |
repeat_interval | integer | — | Repeat every N minutes. Use this OR run_at OR cron. |
Parameters from the server's own tool schema.
An AI agent can call routine_create faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.
Risk signalsAccepts raw HTML/template content (payload) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Create a routine that fires an ops verb on a target machine on a schedule. Pick exactly one of run_at (one-shot), cron (recurring), or repeat_interval (every N minutes). Machine can be 'local' (this agent), 'primary' (the user's primary device alias), or any peer deviceId — peer routing uses the existing P2P relay. The verb must be one of the registered ops verbs (call ops_verbs to list). It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
routine_create accepts 8 parameters: cron, name, verb, run_at, machine, payload, max_runs, repeat_interval. Required: verb. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for routine_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 Yaver. Nothing to install.
routine_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 routine_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 routine_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.
routine_create is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.