分页列出所有执行记录。支持 limit 和 offset 参数，防止返回过多数据导致 Token 爆炸。
AI agents call cron_list_executions to retrieve information from MCP Cron Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries execution history records in a paginated manner. It does not create, modify, delete, or execute tasks—it only fetches and displays existing log data. The parameters (limit, offset) are designed for safe data retrieval without side effects. Therefore, it falls squarely in the Read category with low severity.
From the tool's definition Tool description states '分页列出所有执行记录' (paginate and list all execution records). The terms 'list' and 'executions' with 'limit' and 'offset' parameters indicate read-only retrieval of historical data with pagination, causing no side effects.
Attacks that exploit this kind of access
分页列出所有执行记录。支持 limit 和 offset 参数，防止返回过多数据导致 Token 爆炸。. It is categorised as a Read tool in the MCP Cron Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Cron Server MCP server in PolicyLayer and add a rule for cron_list_executions: 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 MCP Cron Server. Nothing to install.
cron_list_executions 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_list_executions 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_list_executions. 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_list_executions is provided by the MCP Cron Server MCP server (nolan57/opencode-mcp-cron). 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 →