cron_approve · MCP Cron Server MCP: Risk & Policy

WHAT IT DOES

What cron_approve does on MCP Cron Server

AI agents invoke cron_approve to trigger actions in MCP Cron Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why cron_approve needs a policy

This tool approves a scheduled task for execution, which triggers or authorizes external operations to run. Approving execution can cause arbitrary side effects depending on what the cron job does, making Execute the most appropriate category. The blast radius is high because approving a malicious or unintended job could trigger destructive, financial, or other harmful operations.

From the tool's definition 批准任务执行（通过审批ID或执行ID） — 'approve task execution'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cron_approve Rate-limited

cron_approve stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cron_approve": {
      "limits": [
        {
          "counter": "cron_approve_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Cron Server, so you can run agents against it safely.

FAQ

Questions about cron_approve

What does the cron_approve tool do? +

批准任务执行（通过审批ID或执行ID）. It is categorised as a Execute tool in the MCP Cron Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cron_approve? +

Register the MCP Cron Server MCP server in PolicyLayer and add a rule for cron_approve: 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.

What risk level is cron_approve? +

cron_approve is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit cron_approve? +

Yes. Add a rate_limit block to the cron_approve 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.

How do I block cron_approve completely? +

Set action: deny in the PolicyLayer policy for cron_approve. 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.

What MCP server provides cron_approve? +

cron_approve 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.