AI agents call get_app_release_stage_pipeline_job_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 |
|---|---|---|---|
jobId | string | Yes | Pipeline job ID. Typically discovered from the pipeline run details. |
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. |
releaseStageSn | string | Yes | Release stage serial number. Use list_app_release_stage_briefs to discover valid values. |
executionNumber | string | Yes | Release stage execution number. Use list_app_release_stage_runs to discover valid values. |
releaseWorkflowSn | string | Yes | Release workflow serial number. Use list_app_release_workflows to discover valid values. |
Parameters from the server's own tool schema.
This tool queries and retrieves historical log data from a CI/CD pipeline execution. Reading logs has minimal blast radius—it may expose sensitive information in logs (credentials, source code snippets) but does not modify infrastructure, execute operations, or cause destructive changes. This is clearly a Read operation with low severity as it merely retrieves existing data.
From the tool's definition The tool retrieves 'pipeline job log' and 'detailed CI/CD pipeline output' with no mention of modification, deletion, or execution capabilities. The verb 'Get' and the singular purpose of fetching logs indicate a read-only operation.
Attacks that exploit this kind of access
Get the pipeline job log for an AppStack release stage execution. Job logs contain detailed CI/CD pipeline output for a specific job. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_app_release_stage_pipeline_job_log accepts 6 parameters: jobId, appName, organizationId, releaseStageSn, executionNumber, releaseWorkflowSn. Required: jobId, appName, releaseStageSn, executionNumber, releaseWorkflowSn. 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_app_release_stage_pipeline_job_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_app_release_stage_pipeline_job_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_app_release_stage_pipeline_job_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_app_release_stage_pipeline_job_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_app_release_stage_pipeline_job_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 →