advance_workflow
Advance a workflow past a human checkpoint — approve or reject the paused step so the pipeline continues. Use the session id from run_workflow / get_workflow_session. Requires authentication.
This record as markdown: /tools/com-meta-council-decision-intelligence/advance-workflow.md
What advance_workflow does on Meta Council
AI agents call advance_workflow to retrieve information from Meta Council without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
notes | string | — | Optional reviewer notes recorded with the decision. |
action | string | Yes | Explicit checkpoint decision: 'approve' or 'reject'. |
session_id | string | Yes | The workflow session id (must be awaiting a checkpoint). |
expected_step_id | string | — | For routed workflows, the paused result step_id returned by get_workflow_session. |
expected_execution_seq | integer | — | For routed workflows, the paused result execution_seq returned by get_workflow_session. |
Parameters from the server's own tool schema.
Why advance_workflow is rated Low
Even though advance_workflow only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs advance_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 advance_workflow, this is the rule to start with:
advance_workflow is read-only, so it stays allowed. 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 advance_workflow call is checked against it from then on.
Questions about advance_workflow
Advance a workflow past a human checkpoint — approve or reject the paused step so the pipeline continues. Use the session id from run_workflow / get_workflow_session. Requires authentication. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
advance_workflow accepts 5 parameters: notes, action, session_id, expected_step_id, expected_execution_seq. Required: action, 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 advance_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.
advance_workflow is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the advance_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 advance_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.
advance_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.
This server
Across the catalogue