AI agents call list_releases to retrieve information from Mcp Gitee without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | number | — | Current page number |
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) |
per_page | number | — | Number of results per page, maximum 100 |
direction | string | — | Optional. Ascending/descending. Not filled in is ascending |
Parameters from the server's own tool schema.
This tool performs a read-only operation on repository release data. It retrieves and lists existing releases without creating, modifying, or deleting any data. The action is passive with no side effects or blast radius if misused by an AI agent.
From the tool's definition Tool name 'list_releases' and description 'List repository releases' indicate a query operation that retrieves release information without modification.
Attacks that exploit this kind of access
List repository releases. It is categorised as a Read tool in the Mcp Gitee MCP Server, which means it retrieves data without modifying state.
list_releases accepts 5 parameters: page, repo, owner, per_page, direction. 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 list_releases: 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.
list_releases is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_releases 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 list_releases. 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.
list_releases 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 →