Transfer a repository to a new owner
AI agents use transfer_repo 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.
Transferring a repository changes its ownership, which is a significant modification but not inherently irreversible (it can be transferred back). However, it has high blast radius as it changes access control, URLs, and permissions for the entire repository. It's a Write operation (ownership update) rather than Destructive since the repository and its data are preserved.
From the tool's definition Transfer a repository to a new owner
Documented attack patterns abuse exactly the kind of access transfer_repo 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 transfer_repo:
{
"version": "1",
"default": "deny",
"tools": {
"transfer_repo": {
"limits": [
{
"counter": "transfer_repo_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}transfer_repo 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.
Free to start. No card required.
Transfer a repository to a new owner. 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 transfer_repo: 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.
transfer_repo 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 transfer_repo 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 transfer_repo. 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.
transfer_repo 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.