cron_reject · MCP Cron Server MCP: Risk & Policy

WHAT IT DOES

What cron_reject does on MCP Cron Server

AI agents use cron_reject to create or update resources in MCP Cron Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Cron Server environment.

WHY IT NEEDS A POLICY

Why cron_reject needs a policy

This tool reversibly modifies the state of a scheduled cron task by rejecting it (likely marking it as denied or unapproved), similar to how 'cron_approve' would mark it approved. This is Write-category because the effect is reversible (a rejected task can typically be re-approved or resubmitted), and it does not execute code or destructively delete data.

From the tool's definition Tool name 'cron_reject' and description '拒绝任务执行' (reject/deny task execution) indicate modification of scheduled task state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cron_reject Rate-limited

cron_reject stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_reject": {
      "limits": [
        {
          "counter": "cron_reject_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_reject

What does the cron_reject tool do? +

拒绝任务执行. It is categorised as a Write tool in the MCP Cron Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cron_reject? +

Register the MCP Cron Server MCP server in PolicyLayer and add a rule for cron_reject: 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_reject? +

cron_reject is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cron_reject? +

Yes. Add a rate_limit block to the cron_reject 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_reject completely? +

Set action: deny in the PolicyLayer policy for cron_reject. 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_reject? +

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