github_transfer_repo

Transfer a repository to a different user or organization.

SERVERGithub SOURCEdkeeno/github-mcp-server

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dkeeno-github-mcp-server/github-transfer-repo.md

WHAT IT DOES

What github_transfer_repo does on Github

AI agents use github_transfer_repo to commit financial operations through Github, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why github_transfer_repo is rated Critical

github_transfer_repo moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_transfer_repo safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Github, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_transfer_repo, this is the rule to start with:

github_transfer_repo Approval-gated

Any call to github_transfer_repo is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "github_transfer_repo": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about github_transfer_repo

What does the github_transfer_repo tool do? +

Transfer a repository to a different user or organization. It is categorised as a Financial tool in the Github MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on github_transfer_repo? +

Register the Github MCP server in PolicyLayer and add a rule for github_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 Github. Nothing to install.

What risk level is github_transfer_repo? +

github_transfer_repo is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit github_transfer_repo? +

Yes. Add a rate_limit block to the github_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 github_transfer_repo completely? +

Set action: deny in the PolicyLayer policy for github_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 github_transfer_repo? +

github_transfer_repo is provided by the Github MCP server (dkeeno/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Github, and thousands of servers like it.

This server

All 69 Github tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →