AI agents call find_task_operation_log 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. |
taskSn | string | Yes | Deployment task serial number. Typically returned in change order stage details. |
appName | string | Yes | Application name. Use list_applications to discover valid app names. |
stageSn | string | Yes | Deployment stage serial number. Typically returned in change order job details. |
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 retrieves and queries historical deployment task operation logs. It has no capability to modify, delete, execute commands, or trigger financial transactions. The blast radius of misuse is minimal—an agent could only gain visibility into past deployment operations, which is a read-level concern. No reversible or irreversible modifications are possible through this tool.
From the tool's definition Tool description states it 'Get[s] an AppStack deployment task operation log', which is a retrieval operation with no modification capability. The word 'Get' and 'operation log' (a record of past actions) indicate read-only access to historical data.
Attacks that exploit this kind of access
Get an AppStack deployment task operation log. Operation logs record manual or automated actions taken during deployment. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
find_task_operation_log accepts 6 parameters: jobSn, taskSn, appName, stageSn, changeOrderSn, organizationId. Required: jobSn, taskSn, appName, stageSn, 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 find_task_operation_log: 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.
find_task_operation_log 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 find_task_operation_log 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 find_task_operation_log. 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.
find_task_operation_log 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 →