retry_workflow
Continue a stalled or finished workflow run from a chosen step. This starts a NEW run that reuses the outputs the original run already recorded and only executes — and only pays for — the steps from 'from_step' onward. The original run is left untouched and the new one records which run it contin...
This record as markdown: /tools/com-meta-council-decision-intelligence/retry-workflow.md
What retry_workflow does on Meta Council
AI agents invoke retry_workflow to trigger actions in Meta Council. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
from_step | integer | — | Zero-based index of the first step to actually execute. Defaults to the first step with no recorded output. |
session_id | string | Yes | The workflow session id to continue from. |
Parameters from the server's own tool schema.
Why retry_workflow is rated High
retry_workflow triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs retry_workflow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For retry_workflow, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every retry_workflow call is checked against it from then on.
Questions about retry_workflow
Continue a stalled or finished workflow run from a chosen step. This starts a NEW run that reuses the outputs the original run already recorded and only executes — and only pays for — the steps from 'from_step' onward. The original run is left untouched and the new one records which run it continues. Omit 'from_step' to resume at the first step that has no recorded output. A step whose output was never recorded is re-run, never skipped. Requires authentication. It is categorised as a Execute tool in the Meta Council MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
retry_workflow accepts 2 parameters: from_step, session_id. Required: session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council 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 Meta Council. Nothing to install.
retry_workflow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
retry_workflow is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
Across the catalogue