AI agents call get_repo_issue_detail 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 |
|---|---|---|---|
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) |
number | string | Yes | Issue number (case sensitive, no # prefix needed) |
Parameters from the server's own tool schema.
This tool retrieves issue metadata and details from a Gitee repository without modifying, creating, or deleting any data. It has no side effects and poses minimal risk if invoked by an AI agent, as it only exposes existing issue information that the agent already has access to. Classification as Read is appropriate.
From the tool's definition Tool name 'get_repo_issue_detail' and description 'Get the detail of an issue' indicate a retrieval operation. The verb 'get' and lack of any modification language confirm this is a read-only query.
Attacks that exploit this kind of access
Get the detail of an issue. It is categorised as a Read tool in the Mcp Gitee MCP Server, which means it retrieves data without modifying state.
get_repo_issue_detail accepts 3 parameters: repo, owner, number. Required: repo, owner, number. 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 get_repo_issue_detail: 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.
get_repo_issue_detail 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 get_repo_issue_detail 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 get_repo_issue_detail. 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.
get_repo_issue_detail 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 →