获取待审批的任务列表
AI agents call cron_get_approvals 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 a list of pending approval tasks. It is a read-only operation that queries data without modifying, deleting, or executing anything. The description explicitly indicates a 'get' operation, which is characteristic of Read category tools. No blast radius for misuse beyond information disclosure of pending task approvals.
From the tool's definition Tool name 'cron_get_approvals' and description '获取待审批的任务列表' (get list of pending approval tasks) indicate a query/retrieval operation with no 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_approvals: 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_approvals 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_approvals 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_approvals. 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_approvals 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 →