# 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.

Agent View of the PolicyLayer registry record for `cron_next`. HTML page: https://policylayer.com/tools/com-fluentedi-tools/cron-next

## Facts

- Tool: `cron_next`
- Server: Tools (`https://fluentedi.com/mcp`) — https://policylayer.com/tools/com-fluentedi-tools.md
- Homepage: https://github.com/https://fluentedi.com/mcp
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 4 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `from` | string | no | Compute run times after this instant instead of now. |
| `count` | integer | no | How many upcoming run times to return. |
| `timezone` | string | no | 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.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "cron_next",
    "arguments": {
      "expression": "<expression>"
    }
  }
}
```

## 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 signals: Accepts freeform code/query input (expression)

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Tools:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cron_next": {
      "limits": [
        {
          "counter": "cron_next_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Tools (16)

- `edi_build` — Execute — https://policylayer.com/tools/com-fluentedi-tools/edi-build.md
- `edi_parse` — Execute — https://policylayer.com/tools/com-fluentedi-tools/edi-parse.md
- `edi_validate` — Read — https://policylayer.com/tools/com-fluentedi-tools/edi-validate.md
- `hash` — Read — https://policylayer.com/tools/com-fluentedi-tools/hash.md
- `http_assert` — Read — https://policylayer.com/tools/com-fluentedi-tools/http-assert.md
- `http_check` — Read — https://policylayer.com/tools/com-fluentedi-tools/http-check.md
- `json_query` — Read — https://policylayer.com/tools/com-fluentedi-tools/json-query.md
- `json_repair` — Read — https://policylayer.com/tools/com-fluentedi-tools/json-repair.md
- `math_eval` — Read — https://policylayer.com/tools/com-fluentedi-tools/math-eval.md
- `time_diff` — Read — https://policylayer.com/tools/com-fluentedi-tools/time-diff.md
- `time_now` — Read — https://policylayer.com/tools/com-fluentedi-tools/time-now.md
- `time_window` — Read — https://policylayer.com/tools/com-fluentedi-tools/time-window.md
- `tool_describe` — Read — https://policylayer.com/tools/com-fluentedi-tools/tool-describe.md
- `tool_search` — Read — https://policylayer.com/tools/com-fluentedi-tools/tool-search.md
- `time_convert` — Write — https://policylayer.com/tools/com-fluentedi-tools/time-convert.md
- `tool_call` — Write — https://policylayer.com/tools/com-fluentedi-tools/tool-call.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-fluentedi-tools · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-fluentedi-tools