AI agents call cron_task_logs 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 |
|---|---|---|---|
limit | number | — | Max log entries to return (default: 50) |
task_id | string | — | Task ID to get logs for (omit for all agent logs) |
agent_id | string | — | Your agent identifier (default: "default") |
Parameters from the server's own tool schema.
This tool retrieves historical execution logs and status information about cron tasks without modifying, deleting, or executing anything. It is a straightforward data retrieval operation with no side effects. The severity is low because exposure of task logs presents minimal risk—an agent could view scheduling history but cannot alter tasks, execute new commands, or affect system state.
From the tool's definition Tool description states it 'Get execution history/logs for a scheduled task' and 'Shows past completion times, success/failure status, and counts.' The verb 'Get' and the focus on retrieving historical data with no modification capability clearly indicate a…
Attacks that exploit this kind of access
Get execution history/logs for a scheduled task. Shows past completion times, success/failure status, and counts. Omit task_id to get all logs for the agent. It is categorised as a Read tool in the Tools MCP Server, which means it retrieves data without modifying state.
cron_task_logs accepts 3 parameters: limit, task_id, 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_logs: 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_logs 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_logs 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_logs. 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_logs 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 →