Fork a GitHub repository to your account or specified organization
AI agents use fork-repository to create or update resources in GitHub Enterprise MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub Enterprise MCP Server environment.
Forking creates a new repository copy under the user's account or organization. This is a reversible write operation (the fork can be deleted later) that does not destroy or overwrite existing data. It creates a new resource, placing it in the Write category.
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 Enterprise MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitHub Enterprise 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 Enterprise 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 Enterprise MCP Server MCP server (lessinthought/github-enterprice-mcp). 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 →