Parse a standard 5-field cron expression (minute hour day month weekday). Returns: human-readable description, validation status, next 5 run times. E.g. "*/5 9-17 * * 1-5" → "Every 5 minutes from 9am to 5pm, Mon-Fri".
Accepts freeform code/query input (expression); Bulk/mass operation — affects multiple targets
Part of the Timestamp MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke parse_cron to trigger processes or run actions in Timestamp. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
parse_cron can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
parse_cron:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Timestamp policy for all 5 tools.
Agents calling execute-class tools like parse_cron have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
parse_cron is one of the high-risk operations in Timestamp. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Parse a standard 5-field cron expression (minute hour day month weekday). Returns: human-readable description, validation status, next 5 run times. E.g. "*/5 9-17 * * 1-5" → "Every 5 minutes from 9am to 5pm, Mon-Fri".. It is categorised as a Execute tool in the Timestamp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for parse_cron. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Timestamp MCP server.
parse_cron 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 parse_cron rule in your Intercept 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 Intercept policy for parse_cron. 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.
parse_cron is provided by the Timestamp MCP server (openclaw-ai/timestamp-converter). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept