get_pipeline_job_run_log
[Pipeline Management] Get the execution logs of a pipeline job. Retrieve the log content for a specific job in a pipeline run.
This record as markdown: /tools/alibabacloud-devops/get-pipeline-job-run-log.md
What get_pipeline_job_run_log does on Alibabacloud Devops
AI agents call get_pipeline_job_run_log to retrieve information from Alibabacloud Devops without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_pipeline_job_run_log is rated Low
This tool only retrieves and reads log data from completed or ongoing pipeline job executions. It has no capability to modify, delete, execute, or create anything. The worst-case misuse scenario is an AI agent reading logs it shouldn't have access to (information disclosure), which is a low-severity risk assuming proper access controls are enforced upstream.
From the tool's definition Tool description states 'Get the execution logs' and 'Retrieve the log content' — both retrieval operations with no modification or execution capability. The tool queries existing pipeline job run logs without side effects.
Attacks that exploit this kind of access
The rule that runs get_pipeline_job_run_log safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Alibabacloud Devops, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_pipeline_job_run_log, this is the rule to start with:
get_pipeline_job_run_log is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Alibabacloud Devops, apply this rule, and every get_pipeline_job_run_log call is checked against it from then on.
Questions about get_pipeline_job_run_log
[Pipeline Management] Get the execution logs of a pipeline job. Retrieve the log content for a specific job in a pipeline run. It is categorised as a Read tool in the Alibabacloud Devops MCP Server, which means it retrieves data without modifying state.
Register the Alibabacloud Devops 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 Alibabacloud Devops. 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 Alibabacloud Devops MCP server (alibabacloud-devops-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Alibabacloud Devops, and thousands of servers like it.
This server
Across the catalogue