Get a runner registration token (requires admin privileges)
AI agents call get_runner_registration_token to retrieve information from Forgejo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves (rather than modifies or deletes) a registration token used for CI/CD runners. While it is a Read operation, the severity is high because registration tokens are sensitive credentials that could enable an attacker to register malicious runners to execute arbitrary code in the CI/CD pipeline if compromised.
From the tool's definition Tool name 'get_runner_registration_token' and description 'Get a runner registration token' indicate retrieval of an authentication token. The phrase 'requires admin privileges' confirms it retrieves sensitive credentials.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access get_runner_registration_token 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 get_runner_registration_token:
{
"version": "1",
"default": "deny",
"tools": {
"get_runner_registration_token": {}
}
}get_runner_registration_token is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a runner registration token (requires admin privileges). It is categorised as a Read tool in the Forgejo MCP Server, which means it retrieves data without modifying state.
Register the Forgejo MCP server in PolicyLayer and add a rule for get_runner_registration_token: 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.
get_runner_registration_token is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_runner_registration_token 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 get_runner_registration_token. 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.
get_runner_registration_token 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.