AI agents call list_change_request_patch_sets 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 | Merge request local ID within the repository. Use list_change_requests to discover valid local IDs. |
repositoryId | string | Yes | Repository numeric ID or full path such as org/repo. Use list_repositories to discover valid repositories. |
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 performs a query/list operation on historical change data within a version control system (CodeUp merge requests). It retrieves information about diff iterations for review purposes only, causing no side effects, data modification, or external operations.
From the tool's definition The tool "list_change_request_patch_sets" retrieves and lists patch sets (diff iterations) for a merge request.
Attacks that exploit this kind of access
List patch sets (diff iterations) for a CodeUp merge request. Use this to review how a merge request evolved across multiple pushes. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_change_request_patch_sets accepts 3 parameters: localId, repositoryId, organizationId. 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 list_change_request_patch_sets: 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.
list_change_request_patch_sets 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_change_request_patch_sets 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_change_request_patch_sets. 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_change_request_patch_sets 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 →