Run a cron task by name (requires admin privileges)
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.
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
Documented attack patterns abuse exactly the kind of access admin_run_cron_job gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Forgejo, and nothing reaches the server without passing your rules. This is the rule we recommend for admin_run_cron_job:
{
"version": "1",
"default": "deny",
"tools": {
"admin_run_cron_job": {
"limits": [
{
"counter": "admin_run_cron_job_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}admin_run_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.
Free to start. No card required.
Run a cron task by name (requires admin privileges). It is categorised as a Execute tool in the Forgejo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Forgejo MCP server in PolicyLayer and add a rule for admin_run_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 Forgejo. Nothing to install.
admin_run_cron_job is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the admin_run_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.
Set action: deny in the PolicyLayer policy for admin_run_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.
admin_run_cron_job is provided by the Forgejo MCP server (sqcows/forgejo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Forgejo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
103 Forgejo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.