schedule_task
Schedule a task to run at a specific time or on a recurring basis. Supports one-shot (runAt), interval-based (repeatInterval in minutes), and cron expressions.
This record as markdown: /tools/io-github-kivanccakmak-yaver/schedule-task.md
What schedule_task does on Yaver
AI agents invoke schedule_task to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
cron | string | — | Cron expression (minute hour day month weekday), e.g. '0 9 * * 1-5' for weekdays at 9am |
title | string | Yes | Task prompt |
run_at | string | — | ISO8601 datetime for one-shot execution (e.g. '2026-03-22T15:00:00Z') |
runner | string | — | Runner ID (claude, codex, aider, etc.) |
max_runs | integer | — | Maximum number of runs (0 = unlimited) |
repeat_interval | integer | — | Repeat every N minutes |
Parameters from the server's own tool schema.
Why schedule_task is rated High
This tool schedules and triggers execution of arbitrary tasks, which can have wide-ranging side effects depending on what tasks are scheduled. The ability to set recurring cron jobs or interval-based execution amplifies the blast radius significantly, as a misused schedule could repeatedly trigger harmful operations. This falls under Execute as it runs external operations whose effects depend on arguments.
From the tool's definition 'Schedule a task to run at a specific time or on a recurring basis' — triggers execution of tasks either immediately at a specified time or repeatedly via cron/interval
Attacks that exploit this kind of access
The rule that runs schedule_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For schedule_task, this is the rule to start with:
schedule_task stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every schedule_task call is checked against it from then on.
Questions about schedule_task
Schedule a task to run at a specific time or on a recurring basis. Supports one-shot (runAt), interval-based (repeatInterval in minutes), and cron expressions. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
schedule_task accepts 6 parameters: cron, title, run_at, runner, max_runs, repeat_interval. Required: title. 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 schedule_task: 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.
schedule_task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the schedule_task 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_task. 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_task 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.
More on Yaver, and thousands of servers like it.
Across the catalogue