AI agents call get_machine_deploy_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 |
|---|---|---|---|
tunnelId | string | Yes | Deployment tunnel ID. Typically discovered from change order or deployment details. |
machineSn | string | Yes | Machine serial number. Use deployment details to discover valid machine identifiers. |
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 historical deployment log data from a specific machine in a deployment context. It does not create, modify, delete, or execute operations - it only reads and returns existing log information. The blast radius of misuse is low since logs are typically non-sensitive operational data and retrieval causes no state changes.
From the tool's definition Tool description states it 'Get[s] deployment log' - retrieves/queries log data with no side effects. The verb 'Get' and the passive nature of log retrieval indicate a read-only operation.
Attacks that exploit this kind of access
Get deployment log for a specific machine in an AppStack deployment. Machine logs capture the agent-side output of a deployment. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_machine_deploy_log accepts 3 parameters: tunnelId, machineSn, organizationId. Required: tunnelId, machineSn. 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_machine_deploy_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.
get_machine_deploy_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 get_machine_deploy_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 get_machine_deploy_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.
get_machine_deploy_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 →