AI agents use create_repo 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 |
|---|---|---|---|
org | string | — | Organization path (required when owner_type is org) |
name | string | Yes | Repository name |
path | string | — | Repository path (for customization) |
private | boolean | — | Whether the repository is private |
homepage | string | — | Repository homepage |
auto_init | boolean | — | Whether to initialize the repository with a README file |
enterprise | string | — | Enterprise path (required when owner_type is enterprise) |
owner_type | string | Yes | Owner type: user (personal), org (organization), or enterprise |
description | string | — | Repository description |
Parameters from the server's own tool schema.
This tool creates a new repository, which is a reversible Write operation. While repository creation can have organizational implications, it does not delete data (not Destructive), execute arbitrary code (not Execute), or move money (not Financial). The medium severity reflects that an agent could create unwanted repositories or clutter the namespace, but the impact is containable and reversible via deletion.
From the tool's definition Tool name 'create_repo' and description 'Create a repository (user, org, or enterprise)' indicate data creation on a platform (Gitee).
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
Create a repository (user, org, or enterprise). 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.
create_repo accepts 9 parameters: org, name, path, private, homepage, auto_init, enterprise, owner_type, description. Required: name, owner_type. 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 create_repo: 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.
create_repo 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 create_repo 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 create_repo. 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.
create_repo 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 →