admin_run_cron_job

What admin_run_cron_job does on Forgejo

AI agents invoke admin_run_cron_job to trigger actions in Forgejo. 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 admin_run_cron_job is rated High

This tool executes predefined cron tasks on the server. While the actual destructive potential depends on what specific cron jobs exist in the system, the act of triggering arbitrary cron job execution constitutes an Execute action. Requires admin privileges, so misuse by a compromised agent with admin access could trigger unintended automation tasks.

From the tool's definition Tool description states 'Run a cron task by name' - the word 'Run' indicates execution of an external operation. Cron jobs typically trigger automated tasks with effects that depend on which job is specified as an argument.

Risk signalsAdmin/system-level operation

The rule that runs admin_run_cron_job safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Forgejo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For admin_run_cron_job, this is the rule to start with:

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

Questions about admin_run_cron_job