schedule_recurring_job · Simple MCP: Risk & Policy

WHAT IT DOES

What schedule_recurring_job does on Simple MCP

AI agents invoke schedule_recurring_job to trigger actions in Simple MCP. 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 schedule_recurring_job needs a policy

The tool name strongly implies it schedules recurring jobs/tasks for automated execution. Scheduling recurring jobs can trigger arbitrary system operations repeatedly, making misuse potentially high impact.

From the tool's definition Tool name 'schedule_recurring_job' on a server described as providing 'job scheduling' and 'system automation capabilities'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

schedule_recurring_job Rate-limited

schedule_recurring_job 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": {
    "schedule_recurring_job": {
      "limits": [
        {
          "counter": "schedule_recurring_job_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 Simple MCP, so you can run agents against it safely.

FAQ

Questions about schedule_recurring_job

What does the schedule_recurring_job tool do? +

schedule_recurring_job. It is categorised as a Execute tool in the Simple MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on schedule_recurring_job? +

Register the Simple MCP server in PolicyLayer and add a rule for schedule_recurring_job: 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 Simple MCP. Nothing to install.

What risk level is schedule_recurring_job? +

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

Can I rate-limit schedule_recurring_job? +

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

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

schedule_recurring_job is provided by the Simple MCP server (karar-hayder/simple-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.