AI agents call list_change_order_job_logs 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 |
|---|---|---|---|
jobSn | string | Yes | Change order job serial number. Typically returned in change order details. |
appName | string | Yes | Application name. Use list_applications to discover valid app names. |
current | number | — | Page number for pagination. Starts at 1. |
pageSize | number | — | Page size for pagination. Supports 1-100. Defaults to 100 when omitted. |
changeOrderSn | string | Yes | Change order serial number. Use list_change_order_versions to discover valid values. |
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 queries and retrieves existing log data from an AppStack change order job without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal blast radius if misused by an AI agent—the worst case would be exposure of sensitive information contained in logs, but no side effects on systems or data integrity would occur.
From the tool's definition The tool 'list_change_order_job_logs' retrieves deployment script output logs with no indication of modification, deletion, or execution capabilities. The verb 'list' combined with 'logs' (historical records) indicates a read-only query operation.
Attacks that exploit this kind of access
List logs for an AppStack change order job. Job logs capture deployment script output. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_change_order_job_logs accepts 6 parameters: jobSn, appName, current, pageSize, changeOrderSn, organizationId. Required: jobSn, appName, changeOrderSn. 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_order_job_logs: 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_order_job_logs 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_order_job_logs 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_order_job_logs. 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_order_job_logs 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 →