list_pipeline_job_historys
[Pipeline Management] Get the execution history of a pipeline task. Retrieve all execution records for a specific task in a pipeline.
This record as markdown: /tools/alibabacloud-devops/list-pipeline-job-historys.md
What list_pipeline_job_historys does on Alibabacloud Devops
AI agents call list_pipeline_job_historys 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 list_pipeline_job_historys is rated Low
This tool queries and retrieves historical data about pipeline task executions. It has no side effects, does not modify state, does not execute tasks, and does not delete data. It is a straightforward read operation against a DevOps API for audit/visibility purposes.
From the tool's definition Tool name contains 'list' and description states 'Get the execution history' and 'Retrieve all execution records' — purely retrieval operations with no modification, deletion, or execution of pipeline tasks.
Attacks that exploit this kind of access
The rule that runs list_pipeline_job_historys 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 list_pipeline_job_historys, this is the rule to start with:
list_pipeline_job_historys 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 list_pipeline_job_historys call is checked against it from then on.
Questions about list_pipeline_job_historys
[Pipeline Management] Get the execution history of a pipeline task. Retrieve all execution records for a specific task in a pipeline. 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 list_pipeline_job_historys: 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.
list_pipeline_job_historys 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 list_pipeline_job_historys 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 list_pipeline_job_historys. 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.
list_pipeline_job_historys 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