resolve_latest_failed_run

Find the latest failed GitHub Actions run for a repository (optional workflow name filter).

Server Agentic CI/CD MCP Orchestrator siddharth-basale/mcpserver
Category Read
Risk class Low
Parameters 00 required

What resolve_latest_failed_run does on Agentic CI/CD MCP Orchestrator

AI agents call resolve_latest_failed_run to retrieve information from Agentic CI/CD MCP Orchestrator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why resolve_latest_failed_run needs a policy

The tool only fetches information about the latest failed GitHub Actions run for a repository. It is a read/query operation with no modifications, executions, or deletions involved.

From the tool's definition "Find the latest failed GitHub Actions run" — retrieves/queries run status data with an optional filter; no side effects described.

Questions about resolve_latest_failed_run

What does the resolve_latest_failed_run tool do? +

Find the latest failed GitHub Actions run for a repository (optional workflow name filter). It is categorised as a Read tool in the Agentic CI/CD MCP Orchestrator MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on resolve_latest_failed_run? +

Register the Agentic CI/CD MCP Orchestrator MCP server in PolicyLayer and add a rule for resolve_latest_failed_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 Agentic CI/CD MCP Orchestrator. Nothing to install.

What risk level is resolve_latest_failed_run? +

resolve_latest_failed_run is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit resolve_latest_failed_run? +

Yes. Add a rate_limit block to the resolve_latest_failed_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 resolve_latest_failed_run completely? +

Set action: deny in the PolicyLayer policy for resolve_latest_failed_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 resolve_latest_failed_run? +

resolve_latest_failed_run is provided by the Agentic CI/CD MCP Orchestrator MCP server (siddharth-basale/mcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

resolve_latest_failed_run is one line of Agentic CI/CD MCP Orchestrator's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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.