test_workflow_step
Run exactly ONE step of a workflow and return what it produced, so you can iterate on a single step's wording without running the steps before it. THIS SPENDS CREDITS EXACTLY LIKE A REAL STEP: the step runs on a real model through the same engine a full run uses and is billed identically -- it is...
This record as markdown: /tools/com-meta-council-decision-intelligence/test-workflow-step.md
What test_workflow_step does on Meta Council
AI agents call test_workflow_step 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 |
|---|---|---|---|
query | string | — | The input the step works on, exactly as you would pass it to run_workflow. Optional -- omit for a step whose instruction already carries everything it needs. |
workflow | string | Yes | The workflow slug (from list_workflows), e.g. 'due_diligence'. |
parameters | object | — | Optional values for the workflow's declared parameters, as a flat name-to-value object, e.g. {"region": "EU"}. They are substituted into the step wording the sa |
step_index | integer | Yes | Which step to run, counting from 0. A workflow with 4 steps accepts 0 to 3; anything else is refused without spending. |
Parameters from the server's own tool schema.
Why test_workflow_step is rated Low
Even though test_workflow_step 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 test_workflow_step 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 test_workflow_step, this is the rule to start with:
test_workflow_step 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 test_workflow_step call is checked against it from then on.
Questions about test_workflow_step
Run exactly ONE step of a workflow and return what it produced, so you can iterate on a single step's wording without running the steps before it. THIS SPENDS CREDITS EXACTLY LIKE A REAL STEP: the step runs on a real model through the same engine a full run uses and is billed identically -- it is not a simulation, a dry run, or a free preview. If you want to check a workflow's shape, parameters, models and cost estimate for free, use plan_workflow instead; that one runs nothing. Starts no session, so there is nothing to poll and nothing to advance. Requires authentication. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
test_workflow_step accepts 4 parameters: query, workflow, parameters, step_index. Required: workflow, step_index. 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 test_workflow_step: 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.
test_workflow_step 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 test_workflow_step 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 test_workflow_step. 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.
test_workflow_step 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