AI agents call list_merge_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. |
state | string | — | Merge request state: merged, opened, closed, reopened, accepted, canceled, or all. |
search | string | — | Title search keyword. |
orderBy | string | — | Sort field: id or updated_at. |
perPage | number | — | Page size for pagination. Supports 1-100. |
createdAfter | string | — | Created-after date in yyyy-MM-dd format. |
targetBranch | string | — | Target branch filter. |
authorUserIds | array | — | Author user IDs. |
createdBefore | string | — | Created-before date in yyyy-MM-dd format. |
repositoryIds | array | — | Repository IDs as strings to preserve int64 precision. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
assigneeUserIds | array | — | Assignee user IDs. |
Parameters from the server's own tool schema.
This tool retrieves and queries merge request data from repositories without creating, modifying, deleting, or executing anything. It has no side effects and poses minimal risk if misused by an AI agent—the worst outcome would be enumeration of existing merge requests across an organization, which is informational in nature.
From the tool's definition Tool name 'list_merge_requests' and description explicitly states it 'List[s]' merge requests, which is a query/retrieval operation with no modification capability.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
List legacy CodeUp merge requests across repositories in a Yunxiao organization. For change requests (new merge request format), use list_change_requests instead. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_merge_requests accepts 12 parameters: page, state, search, orderBy, perPage, createdAfter, targetBranch, authorUserIds, createdBefore, repositoryIds, organizationId, assigneeUserIds. 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_merge_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_merge_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_merge_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_merge_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_merge_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 →