fork_repository · Server Github MCP: Risk & Policy

WHAT IT DOES

What fork_repository does on Server Github

AI agents use fork_repository to create or update resources in Server Github — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Server Github environment.

PARAMETERS

Parameter	Type	Required	Description
`repo`	string	Yes	Repository name
`owner`	string	Yes	Repository owner (username or organization)
`organization`	string	—	Optional: organization to fork to (defaults to your personal account)

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why fork_repository needs a policy

Forking creates a new repository copy under the user's account or organization. This is a Write operation — it creates a new resource (the forked repo) but does not irreversibly destroy anything. Misuse could clutter an account/org with unwanted repos or be used as part of a supply-chain attack, giving medium severity.

From the tool's definition Fork a GitHub repository to your account or specified organization

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

fork_repository Rate-limited

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.

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Server Github, so you can run agents against it safely.

FAQ

Questions about fork_repository

What does the fork_repository tool do? +

Fork a GitHub repository to your account or specified organization. It is categorised as a Write tool in the Server Github MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does fork_repository accept? +

fork_repository accepts 3 parameters: repo, owner, organization. Required: repo, owner. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on fork_repository? +

Register the Server 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 Server Github. Nothing to install.

What risk level is fork_repository? +

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

Can I rate-limit fork_repository? +

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.

How do I block fork_repository completely? +

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.

What MCP server provides fork_repository? +

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