register_org_runner
Register a new Actions runner for an organization. The response contains the runner token, which is only shown once
This record as markdown: /tools/sqcows-forgejo-mcp/register-org-runner.md
What register_org_runner does on Forgejo
AI agents use register_org_runner to create or update resources in Forgejo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Forgejo environment.
Why register_org_runner is rated Medium
Registers a runner that can execute CI/CD actions, expanding org's execution surface.
From the tool's definition Register a new Actions runner for an organization
Attacks that exploit this kind of access
The rule that runs register_org_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 register_org_runner, this is the rule to start with:
register_org_runner stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 register_org_runner call is checked against it from then on.
Questions about register_org_runner
Register a new Actions runner for an organization. The response contains the runner token, which is only shown once. It is categorised as a Write tool in the Forgejo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Forgejo MCP server in PolicyLayer and add a rule for register_org_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.
register_org_runner is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the register_org_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 register_org_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.
register_org_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.
This server
Across the catalogue