create_fork · GitHub See MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_fork does on GitHub See MCP Server

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

WHY IT NEEDS A POLICY

Why create_fork needs a policy

Creating a fork writes/creates new data (a forked repository) in GitHub but does not delete or destroy existing data, and is reversible (the fork can be deleted). This is a Write-category action. Severity is medium because while forking is generally benign, an agent creating many forks could consume resources or create unintended repository copies that clutter a user's account or organization.

From the tool's definition Tool name is 'create_fork' and description states 'Create a fork of a GitHub repository'. Forking creates a new repository copy under the user's account, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_fork Rate-limited

create_fork 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": {
    "create_fork": {
      "limits": [
        {
          "counter": "create_fork_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 GitHub See MCP Server, so you can run agents against it safely.

FAQ

Questions about create_fork

What does the create_fork tool do? +

Create a fork of a GitHub repository. It is categorised as a Write tool in the GitHub See MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_fork? +

Register the GitHub See MCP Server MCP server in PolicyLayer and add a rule for create_fork: 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 See MCP Server. Nothing to install.

What risk level is create_fork? +

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

Can I rate-limit create_fork? +

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

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

create_fork is provided by the GitHub See MCP Server MCP server (jesusmaster/github-see-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.