fork_repository
Fork a GitHub repository to your account or specified organization
This record as markdown: /tools/github/fork-repository.md
What fork_repository does on GitHub
AI agents use fork_repository to create or update resources in GitHub, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
repo | string | — | Repository name |
owner | string | — | Repository owner |
organization | string | — | Organization to fork to |
Parameters from the server's own tool schema.
Why fork_repository is rated Medium
Forking creates a new copy of a repository under a different account or organization. This is a Write operation as it creates new data (a new repository fork) but is reversible — the fork can be deleted later. It does not delete or overwrite existing data, execute code, or involve financial transactions. Misuse could lead to unauthorized forks of private repositories or storage consumption, hence medium severity.
From the tool's definition Fork a GitHub repository to your account or specified organization
Attacks that exploit this kind of access
The rule that runs fork_repository 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 fork_repository, this is the rule to start with:
fork_repository 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 GitHub, apply this rule, and every fork_repository call is checked against it from then on.
Questions about fork_repository
Fork a GitHub repository to your account or specified organization. It is categorised as a Write tool in the GitHub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
fork_repository accepts 3 parameters: repo, owner, organization. The full parameter table on this page comes from the server's own tool schema.
Register the GitHub MCP server in PolicyLayer and add a rule for fork_repository: 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.
fork_repository 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 fork_repository 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 fork_repository. 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.
fork_repository is provided by the GitHub MCP server (oci:ghcr.io/github/github-mcp-server:1.3.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue