transfer_repo

Transfer a repository to a new owner

SERVERForgejo SOURCEsqcows/forgejo-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sqcows-forgejo-mcp/transfer-repo.md

WHAT IT DOES

What transfer_repo does on Forgejo

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.

RISK

Why transfer_repo is rated Medium

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs transfer_repo 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 transfer_repo, this is the rule to start with:

transfer_repo Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transfer_repo": {
      "limits": [
        {
          "counter": "transfer_repo_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Forgejo, apply this rule, and every transfer_repo call is checked against it from then on.

FAQ

Questions about transfer_repo

What does the transfer_repo tool do? +

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.

How do I enforce a policy on transfer_repo? +

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.

What risk level is transfer_repo? +

transfer_repo is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit transfer_repo? +

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.

How do I block transfer_repo completely? +

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.

What MCP server provides transfer_repo? +

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.

KEEP EXPLORING

More on Forgejo, and thousands of servers like it.

This server

All 457 Forgejo tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →