AI agents call list_change_requests 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 |
|---|---|---|---|
page | number | — | Page number for pagination. Starts at 1. |
sort | string | — | Sort direction: asc (ascending) or desc (descending). |
state | string | — | Merge request state: opened, merged, or closed. |
search | string | — | Title search keyword. |
orderBy | string | — | Sort field: created_at or updated_at. |
perPage | number | — | Page size for pagination. Supports 1-100. Defaults to 100 when omitted. |
authorIds | string | — | Comma-separated author user IDs. |
projectIds | string | — | Comma-separated repository IDs or full paths (e.g., org/repo). Use list_repositories to discover repositories. |
reviewerIds | string | — | Comma-separated reviewer user IDs. |
createdAfter | string | — | Created-after time in ISO 8601 format. |
createdBefore | string | — | Created-before time in ISO 8601 format. |
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 and displays existing change request metadata (merge requests) for visibility and tracking purposes. It performs a read-only query across repositories without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal — an AI agent could only enumerate pending reviews or merged changes, which does not compromise system integrity or data security.
From the tool's definition Tool name 'list_change_requests' and description 'List CodeUp change requests (merge requests) across repositories' — the verb 'list' and the stated purpose of finding and tracking changes indicate retrieval/query operations with no side effects.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
List CodeUp change requests (merge requests) across repositories in a Yunxiao organization. Use this to find pending reviews or track merged changes. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_change_requests accepts 12 parameters: page, sort, state, search, orderBy, perPage, authorIds, projectIds, reviewerIds, createdAfter, createdBefore, organizationId. 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_requests: 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_requests 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_requests 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_requests. 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_requests 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 →