cron_next
Parses a standard 5-field cron expression (or 6-field with leading seconds, or a macro like @daily), validates it, describes it in plain English, and computes the next run times in a given timezone with daylight-saving handled. Use it before writing a schedule to config — cron's day-of-month/day-...
This record as markdown: /tools/com-fluentedi-tools/cron-next.md
What cron_next does on Tools
AI agents invoke cron_next to trigger actions in Tools. 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 |
|---|---|---|---|
from | string | — | Compute run times after this instant instead of now. |
count | integer | — | How many upcoming run times to return. |
timezone | string | — | IANA timezone the schedule runs in. |
expression | string | Yes | Cron expression, e.g. "*/15 * * * *", "0 9 * * 1-5", "@daily". |
Parameters from the server's own tool schema.
Why cron_next is rated High
cron_next 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 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cron_next, this is the rule to start with:
cron_next 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 Tools, apply this rule, and every cron_next call is checked against it from then on.
Questions about cron_next
Parses a standard 5-field cron expression (or 6-field with leading seconds, or a macro like @daily), validates it, describes it in plain English, and computes the next run times in a given timezone with daylight-saving handled. Use it before writing a schedule to config — cron's day-of-month/day-of-week OR-semantics and step syntax are a common source of silently wrong schedules. It is categorised as a Execute tool in the Tools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
cron_next accepts 4 parameters: from, count, timezone, expression. Required: expression. The full parameter table on this page comes from the server's own tool schema.
Register the Tools MCP server in PolicyLayer and add a rule for cron_next: 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 Tools. Nothing to install.
cron_next 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 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. 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 is provided by the Tools MCP server (https://fluentedi.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tools, and thousands of servers like it.
This server
Across the catalogue