AI agents call cron_task_list 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 |
|---|---|---|---|
due | boolean | — | Only show tasks due now (default: false) |
tag | string | — | Filter by tag (optional) |
agent_id | string | — | Your agent identifier (default: "default") |
Parameters from the server's own tool schema.
The tool retrieves and queries existing cron task data without creating, modifying, deleting, or executing any tasks. It is purely informational. Severity is low because listing tasks poses minimal security risk—an AI agent gaining this capability cannot alter system state or cause unintended actions, only view scheduled work metadata.
From the tool's definition Tool description states 'List scheduled tasks' with optional filtering by due status. This is a read-only query operation with no data modification, execution, or side effects.
Attacks that exploit this kind of access
List scheduled tasks. Use due=true to see only tasks that need action now. It is categorised as a Read tool in the Tools MCP Server, which means it retrieves data without modifying state.
cron_task_list accepts 3 parameters: due, tag, agent_id. 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_task_list: 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_task_list 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_task_list 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_task_list. 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_task_list 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 →