retry-workflow · Stage0 Authorization MCP Server MCP

WHAT IT DOES

What retry-workflow does on Stage0 Authorization MCP Server

AI agents invoke retry-workflow to trigger actions in Stage0 Authorization MCP Server. 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 IT NEEDS A POLICY

Why retry-workflow needs a policy

This tool executes a workflow (an external operation whose effects depend on context and arguments), placing it in the Execute category. Severity is high because retrying workflows could consume resources, trigger downstream integrations, or repeat partially-completed operations.

From the tool's definition 'Retry a failing workflow' describes an action that triggers external operations—specifically re-executing a previously-failed workflow.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

retry-workflow Rate-limited

retry-workflow stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "retry-workflow": {
      "limits": [
        {
          "counter": "retry-workflow_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Stage0 Authorization MCP Server, so you can run agents against it safely.

FAQ

Questions about retry-workflow

What does the retry-workflow tool do? +

Retry a failing workflow (MEDIUM RISK - may DEFER if loop threshold exceeded). It is categorised as a Execute tool in the Stage0 Authorization MCP Server 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-workflow? +

Register the Stage0 Authorization MCP Server MCP server in PolicyLayer and add a rule for retry-workflow: 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 Stage0 Authorization MCP Server. Nothing to install.

What risk level is retry-workflow? +

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

Can I rate-limit retry-workflow? +

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

Set action: deny in the PolicyLayer policy for retry-workflow. 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-workflow? +

retry-workflow is provided by the Stage0 Authorization MCP Server MCP server (starlight143/mcp-server-stage0-authorization). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.