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".
Risk signalsAccepts freeform code/query input (expression) · Bulk/mass operation — affects multiple targets
Part of the Timestamp server.
Free to start. No card required.
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. PolicyLayer 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.
{
"version": "1",
"default": "deny",
"tools": {
"parse_cron": {
"limits": [
{
"counter": "parse_cron_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Timestamp policy for all 5 tools.
These attack patterns abuse exactly the kind of access parse_cron gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
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.
Register the Timestamp MCP server in PolicyLayer and add a rule for parse_cron: 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 Timestamp. Nothing to install.
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 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 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). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Timestamp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.