run_workflow
Advance a planned workflow, pausing at approval gates for human decision, then continue by dispatching remaining steps for agent execution.
Instructions
[WRITE] Advance a planned workflow. Pauses at approval gates.
IMPORTANT — this MCP server has no dispatcher and cannot call other skills' MCP tools itself. Steps are recorded as 'not_executed' and the run finishes with outcome='dispatch_required' (NOT 'completed'), returning each pending step's skill/tool/params. YOU (the calling agent) must then perform those skill/tool calls in order. A workflow only reaches 'completed' when every step genuinely executed via a real dispatcher (embedders supplying one to WorkflowExecutor).
Safety: the workflow is structurally reviewed before each run. Runs are REFUSED if review finds ungated destructive steps or destructive steps inside a parallel group, unless force=True (forced runs are written to the workflow audit log).
When an approval gate is reached, the workflow pauses with state 'awaiting_approval'. Call approve() to continue.
Args: workflow_id: The workflow ID from plan_workflow. force: Bypass blocking review findings (ungated_destructive, destructive_in_parallel_group). Use only with explicit human consent; the bypass is audited.
Returns: Current workflow state with 'outcome' (completed | awaiting_approval | dispatch_required | failed) and, when dispatch is required, a 'pending_dispatch' list of steps for the agent to perform.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| workflow_id | Yes | ||
| force | No |