cron_next_runs
utilpeek: the next run times of a cron expression. For iCalendar RRULEs use expand_rrule. Standard 5-field cron (minute hour day-of-month month day-of-week) or a macro (@daily, @hourly, ...); no seconds or year fields, no R/H/W. Day-of-month and day-of-week use Vixie OR semantics; an expression t...
This record as markdown: /tools/dev-tanod-tanod/cron-next-runs.md
What cron_next_runs does on Tanod
AI agents invoke cron_next_runs to trigger actions in Tanod. 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 |
|---|---|---|---|
count | integer | — | Number of next runs (1-50, default 10). |
start | object | — | Optional ISO 8601 start (default now). |
timezone | object | — | Optional IANA time zone (default UTC). |
expression | string | Yes | 5-field cron expression or macro, e.g. */15 9-17 * * MON-FRI. |
Parameters from the server's own tool schema.
Why cron_next_runs is rated High
cron_next_runs triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsAccepts freeform code/query input (expression)
Attacks that exploit this kind of access
The rule that runs cron_next_runs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cron_next_runs, this is the rule to start with:
cron_next_runs 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 Tanod, apply this rule, and every cron_next_runs call is checked against it from then on.
Questions about cron_next_runs
utilpeek: the next run times of a cron expression. For iCalendar RRULEs use expand_rrule. Standard 5-field cron (minute hour day-of-month month day-of-week) or a macro (@daily, @hourly, ...); no seconds or year fields, no R/H/W. Day-of-month and day-of-week use Vixie OR semantics; an expression that never fires (Feb 30) is a 422 no_next_run (not charged); rare ones return what exists with exhausted: true. An invalid expression, start or zone is a 422 (not charged). Typically under 0.1 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/cron-next-run-api.html. It is categorised as a Execute tool in the Tanod MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
cron_next_runs accepts 4 parameters: count, start, timezone, expression. Required: expression. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for cron_next_runs: 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 Tanod. Nothing to install.
cron_next_runs 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 cron_next_runs 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 cron_next_runs. 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.
cron_next_runs is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
Across the catalogue