获取系统统计信息（任务总数、今日执行次数、平均耗时等）
AI agents call cron_get_stats 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 queries and returns aggregated metrics about cron job performance and system state. It has no side effects, does not execute jobs, does not modify scheduling rules, and does not delete or create tasks. It is a pure data retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states it retrieves system statistics (total tasks, execution count today, average duration, etc.) with no modification or execution capability. The verb '获取' (get/retrieve) and metric-only nature confirm read-only behavior.
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_stats: 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_stats 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_stats 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_stats. 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_stats 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 →