AI agents call list_comments 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 |
order | string | — | Sort direction: asc (default) or desc |
owner | string | Yes | The space address to which the repository belongs (enterprise, organization or personal path) |
since | string | — | Only comments updated at or after this time in ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ |
number | string | Yes | Issue or pull request number (case sensitive, no # prefix needed) |
per_page | number | — | Number of results per page, maximum 100 |
resource_type | string | Yes | Resource type: issue or pull |
Parameters from the server's own tool schema.
This tool queries and retrieves existing comment data from a pull request or issue. It performs no modifications, deletions, or executions. The action is read-only and returns information without altering any state.
From the tool's definition Tool name 'list_comments' and description 'List all comments for an issue or pull request' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all comments for an issue or pull request. It is categorised as a Read tool in the Mcp Gitee MCP Server, which means it retrieves data without modifying state.
list_comments accepts 8 parameters: page, repo, order, owner, since, number, per_page, resource_type. Required: repo, owner, number, resource_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 list_comments: 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_comments 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_comments 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_comments. 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_comments 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 →