AI agents use fork_repository to create or update resources in Mcp Gitee — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Gitee environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | The name of the forked repository, default is the same as the original repository |
path | string | — | The path of the forked repository, default is the same as the original repository |
repo | string | Yes | The path of the repository |
owner | string | Yes | The space address to which the repository belongs (the address path of the enterprise, organization or individual) |
organization | string | — | The full address of the organization space to which the repository belongs, default for current user |
Parameters from the server's own tool schema.
Forking a repository creates a new copy of the repository under the user's account. This is a reversible write operation (the fork can be deleted later), not destructive. It creates new data (a new repository) rather than modifying existing data, and has no financial implications. Severity is medium because misuse could spam an organization's account with unwanted forks.
From the tool's definition Fork a repository
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
Fork a repository. It is categorised as a Write tool in the Mcp Gitee MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
fork_repository accepts 5 parameters: name, path, repo, owner, organization. Required: repo, owner. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Gitee 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 Mcp Gitee. 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 Mcp Gitee MCP server (@gitee/mcp-gitee). 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 →