admin_register_runner
Register a new Actions runner for the instance (requires admin privileges). The response contains the runner token, which is only shown once
This record as markdown: /tools/sqcows-forgejo-mcp/admin-register-runner.md
What admin_register_runner does on Forgejo
AI agents invoke admin_register_runner 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_register_runner is rated High
Registers a runner that executes CI/CD actions; admin-level operation with broad impact.
From the tool's definition Register a new Actions runner for the instance (requires admin privileges)
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs admin_register_runner 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_register_runner, this is the rule to start with:
admin_register_runner 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Forgejo, apply this rule, and every admin_register_runner call is checked against it from then on.
Questions about admin_register_runner
Register a new Actions runner for the instance (requires admin privileges). The response contains the runner token, which is only shown once. 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_register_runner: 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_register_runner 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_register_runner 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_register_runner. 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_register_runner 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.
More on Forgejo, and thousands of servers like it.
Across the catalogue