AI agents call get_pipeline_job_run_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 | Job ID within the pipeline run. Use list_pipeline_jobs_by_category to discover valid job IDs. |
pipelineId | string | Yes | Pipeline ID (string). Use list_pipelines to find the pipeline ID. |
pipelineRunId | string | Yes | Pipeline run ID. Use list_pipeline_runs to discover valid run IDs. |
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 purely retrieves and queries existing log data for debugging purposes. It has no side effects, does not execute pipeline jobs, does not modify infrastructure or configuration, and does not delete data. It fits the 'Read' category as a data retrieval operation with minimal security risk.
From the tool's definition Tool retrieves execution logs for a specific pipeline job run ('Get the execution log', 'inspecting individual job output'). No modification, deletion, or execution of operations is performed—only querying and reading diagnostic information.
Attacks that exploit this kind of access
Get the execution log for a specific job within a Flow pipeline run. Use this to debug pipeline failures by inspecting individual job output. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_pipeline_job_run_log accepts 4 parameters: jobId, pipelineId, pipelineRunId, organizationId. Required: jobId, pipelineId, pipelineRunId. 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_pipeline_job_run_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_pipeline_job_run_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_pipeline_job_run_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_pipeline_job_run_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_pipeline_job_run_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 →