AI agents call get_change_request_overview 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 within the repository. Use list_change_requests to discover valid local IDs. |
commentState | string | — | Comment state filter: OPENED or RESOLVED. Defaults to OPENED. |
repositoryId | string | Yes | Repository ID (numeric ID or full path like org/repo). Use list_repositories to find the repository ID. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
commentResolved | boolean | — | Whether to show resolved comments. Defaults to false. |
includeComments | boolean | — | Whether to include comments. Defaults to true. |
includePatchSets | boolean | — | Whether to include patch sets. Defaults to true. |
Parameters from the server's own tool schema.
This tool retrieves and queries information about a CodeUp change request (merge request) without modifying, deleting, or executing any operations. It is purely informational and presents no risk of unintended data modification or destructive action.
From the tool's definition Tool is described as 'one read-only call' that 'Get a comprehensive overview' of change request data including 'basic info, patch sets, and comments'. The explicit 'read-only' designation confirms retrieval without side effects.
Attacks that exploit this kind of access
Get a comprehensive overview of a CodeUp change request (merge request) including basic info, patch sets, and comments in one read-only call. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_change_request_overview accepts 7 parameters: localId, commentState, repositoryId, organizationId, commentResolved, includeComments, includePatchSets. Required: localId, 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_overview: 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_overview 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_overview 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_overview. 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_overview 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 →