Fork a GitHub repository to your account or specified organization
AI agents use fork_repository to create or update resources in GitHub MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub MCP Server environment.
Forking creates a new copy of a repository under the authenticated user's account or an organization. This is a reversible write operation (the fork can be deleted), not destructive, and has no financial implications. Misuse could lead to unauthorized copies of private repositories or filling up an organization's repository quota, 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
Fork a GitHub repository to your account or specified organization. It is categorised as a Write tool in the GitHub MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitHub MCP Server 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 MCP Server. 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 MCP server (tuanle96/mcp-github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →