AI agents use create_release 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 |
|---|---|---|---|
body | string | Yes | The description of the release |
name | string | Yes | The name of the release |
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) |
tag_name | string | Yes | The name of the tag |
prerelease | boolean | — | Whether the release is a prerelease |
target_commitish | string | Yes | The branch name or commit SHA, defaults to the repository's default branch |
Parameters from the server's own tool schema.
The tool creates a new release artifact in a Gitee repository. This is a Write operation because releases can be deleted or modified after creation (reversible). It is not Execute because it does not run arbitrary code or trigger external operations beyond creating a structured release object.
From the tool's definition Tool name: 'create_release'. Description: 'Create a release'. The Gitee context indicates this is a git repository management server. Creating a release is a reversible write operation that tags a version and publishes release metadata in a repository.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
Create a release. 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_release accepts 7 parameters: body, name, repo, owner, tag_name, prerelease, target_commitish. Required: body, name, repo, owner, tag_name, target_commitish. 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_release: 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_release 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_release 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_release. 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_release 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 →