AI agents call get_merge_request 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 |
|---|---|---|---|
repositoryId | string | Yes | Repository numeric ID or full path such as org/repo. |
mergeRequestId | string | Yes | Merge request local ID. Use list_merge_requests to discover valid IDs. |
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 merge request data by ID. It performs no creation, modification, deletion, code execution, or financial operations. The blast radius of misuse is minimal — an attacker could only view existing merge request details. This is a straightforward Read category tool with low severity.
From the tool's definition Tool description explicitly states 'Get a single legacy CodeUp merge request by ID' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get a single legacy CodeUp merge request by ID. Use list_merge_requests to discover valid merge request IDs. For the new format, use get_change_request_overview instead. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_merge_request accepts 3 parameters: repositoryId, mergeRequestId, organizationId. Required: repositoryId, mergeRequestId. 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_merge_request: 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_merge_request 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_merge_request 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_merge_request. 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_merge_request 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 →