AI agents call list_appstack_change_request_work_items 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 |
|---|---|---|---|
sn | string | Yes | Change request serial number. Typically discovered via list_attached_change_requests. |
appName | string | Yes | Application name. Use list_applications to discover valid app names. |
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 metadata about work items linked to an AppStack change request. It performs a read-only query operation with no side effects, no data modification, no code execution, and no destructive capabilities. The blast radius of misuse is minimal—an agent could only access information already associated with a change request.
From the tool's definition The tool 'list_appstack_change_request_work_items' lists/queries work items associated with a change request. The verb 'list' and phrase 'represent linked' indicate retrieval of existing data without modification or execution of operations.
Attacks that exploit this kind of access
List work items for an AppStack change request. Work items represent linked Projex tasks or requirements. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_appstack_change_request_work_items accepts 3 parameters: sn, appName, organizationId. Required: sn, appName. 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_appstack_change_request_work_items: 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_appstack_change_request_work_items 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_appstack_change_request_work_items 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_appstack_change_request_work_items. 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_appstack_change_request_work_items 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 →