获取任务的执行历史记录
AI agents call cron_get_history 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 historical execution logs of cron jobs. It performs a read-only query operation with no capability to modify, delete, or execute tasks. The blast radius of misuse is minimal—an attacker gains visibility into past executions but cannot alter system state or trigger new actions. Classified as Read with low severity.
From the tool's definition Tool name 'cron_get_history' and description '获取任务的执行历史记录' (get task execution history) indicate data retrieval without side effects.
Attacks that exploit this kind of access
获取任务的执行历史记录. 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_get_history: 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_get_history 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_get_history 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_get_history. 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_get_history 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 →