AI agents call get_appstack_change_request_audit_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. |
refType | string | Yes | Reference type for audit items. Valid values: RELEASE, CHANGE_REQUEST. |
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 audit/approval checkpoint data for a change request without modifying, deleting, or executing any operations. It is purely informational and read-only in nature, consistent with other 'get_*' tools on the server (get_app_orchestration, get_app_release_workflow_overview, etc.). No destructive, financial, or execution capabilities are evident.
From the tool's definition Tool description states it 'Get[s] audit items' and 'represent[s] approval checkpoints' — a retrieval operation with no side effects. The verb 'get' indicates a query operation.
Attacks that exploit this kind of access
Get audit items for an AppStack change request. Audit items represent approval checkpoints that must be satisfied before deployment. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_appstack_change_request_audit_items accepts 4 parameters: sn, appName, refType, organizationId. Required: sn, appName, refType. 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_appstack_change_request_audit_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.
get_appstack_change_request_audit_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 get_appstack_change_request_audit_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 get_appstack_change_request_audit_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.
get_appstack_change_request_audit_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 →