AI agents call get_change_request_comment to retrieve information from Yunxiao without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
localId | string | Yes | Change request local ID. Use list_change_requests to discover valid local IDs. |
commentId | string | Yes | Comment ID. Use list_change_request_comments to discover valid comment IDs. |
repositoryId | string | Yes | Repository numeric ID or full path such as org/repo. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
Parameters from the server's own tool schema.
This tool retrieves existing data (a single comment on a change request) without any side effects, creation, modification, deletion, or code execution. It is a straightforward query operation on the Alibaba Yunxiao DevOps platform, consistent with the 'Read' category.
From the tool's definition Tool description explicitly states 'Get a single comment' and references list_change_request_comments for discovery—both read operations with no modification or execution.
Attacks that exploit this kind of access
Get a single comment on a CodeUp change request by ID. Use list_change_request_comments to discover valid comment IDs. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_change_request_comment accepts 4 parameters: localId, commentId, repositoryId, organizationId. Required: localId, commentId, repositoryId. The full parameter table on this page comes from the server's own tool schema.
Register the Yunxiao MCP server in PolicyLayer and add a rule for get_change_request_comment: 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 Yunxiao. Nothing to install.
get_change_request_comment 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_change_request_comment 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_change_request_comment. 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_change_request_comment is provided by the Yunxiao MCP server (@futuretea/yunxiao-mcp-server). 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 →