resume_cron_job · Nexus Core MCP: Risk & Policy

WHAT IT DOES

What resume_cron_job does on Nexus Core

AI agents invoke resume_cron_job to trigger actions in Nexus Core. 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 resume_cron_job needs a policy

Resuming a cron job causes periodic automated tasks to begin executing again, which is an Execute-category action. The blast radius is medium because the impact depends on what the cron job does, but scoping to the calling user limits broader damage.

From the tool's definition 'Reactivate a paused cron job' — this triggers execution of a scheduled job/task that was previously paused, causing external operations to resume running on a schedule.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resume_cron_job Rate-limited

resume_cron_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": {
    "resume_cron_job": {
      "limits": [
        {
          "counter": "resume_cron_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 Nexus Core, so you can run agents against it safely.

FAQ

Questions about resume_cron_job

What does the resume_cron_job tool do? +

Reactivate a paused cron job. Scoped to the calling user. It is categorised as a Execute tool in the Nexus Core MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on resume_cron_job? +

Register the Nexus Core MCP server in PolicyLayer and add a rule for resume_cron_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 Nexus Core. Nothing to install.

What risk level is resume_cron_job? +

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

Can I rate-limit resume_cron_job? +

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

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

resume_cron_job is provided by the Nexus Core MCP server (noumenon-ai/nexus-core). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.