retry_pipeline_job_run

[Pipeline Management] Retry a failed pipeline job run.

SERVERAlibabacloud Devops SOURCEalibabacloud-devops-mcp-server
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alibabacloud-devops/retry-pipeline-job-run.md

What retry_pipeline_job_run does on Alibabacloud Devops

AI agents invoke retry_pipeline_job_run to trigger actions in Alibabacloud Devops. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why retry_pipeline_job_run is rated High

Retrying a pipeline job run causes external systems (build servers, deployment platforms) to execute code and perform actions. While not destructive or financial in isolation, a failed pipeline job might have partially completed side effects (partial deployments, partial state changes), and retrying could propagate those effects or trigger new operations in development/staging/production environments.

From the tool's definition Tool description states 'Retry a failed pipeline job run' — this triggers execution of a pipeline job, which re-runs code/CI-CD actions whose effects depend on the job's configuration and target environment.

Questions about retry_pipeline_job_run

What does the retry_pipeline_job_run tool do? +

[Pipeline Management] Retry a failed pipeline job run. It is categorised as a Execute tool in the Alibabacloud Devops MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on retry_pipeline_job_run? +

Register the Alibabacloud Devops MCP server in PolicyLayer and add a rule for retry_pipeline_job_run: 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.

What risk level is retry_pipeline_job_run? +

retry_pipeline_job_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit retry_pipeline_job_run? +

Yes. Add a rate_limit block to the retry_pipeline_job_run 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.

How do I block retry_pipeline_job_run completely? +

Set action: deny in the PolicyLayer policy for retry_pipeline_job_run. 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.

What MCP server provides retry_pipeline_job_run? +

retry_pipeline_job_run 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Alibabacloud Devops's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.