AI agents call cron_parse to retrieve information from Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
expression | string | Yes | 5-field cron: min hour day month weekday |
Parameters from the server's own tool schema.
This tool only parses and interprets a cron expression, converting it to a human-readable description and computing upcoming run times. It performs no writes, executions, or side effects — purely a read/analysis operation.
From the tool's definition Parse cron expression to human-readable description with next 5 run times.
Risk signalsAccepts freeform code/query input (expression)
Attacks that exploit this kind of access
Parse cron expression to human-readable description with next 5 run times. It is categorised as a Read tool in the Tools MCP Server, which means it retrieves data without modifying state.
cron_parse accepts 1 parameter: 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_parse: 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_parse is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cron_parse 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_parse. 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_parse is provided by the Tools MCP server (https://www.jiebang.site/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →