run_comparison
Re-run a member's workflow as it stands today and record the result as a new run. This calls model providers and costs money; it is priced and refused against your budget before anything starts. It does not act on the outside world a second time: connector steps are served from the baseline's rec...
This record as markdown: /tools/com-meta-council-decision-intelligence/run-comparison.md
What run_comparison does on Meta Council
AI agents invoke run_comparison 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 |
|---|---|---|---|
set_id | string | Yes | |
baseline_session_id | string | Yes |
Parameters from the server's own tool schema.
Why run_comparison is rated High
run_comparison 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 run_comparison 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 run_comparison, this is the rule to start with:
run_comparison 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 run_comparison call is checked against it from then on.
Questions about run_comparison
Re-run a member's workflow as it stands today and record the result as a new run. This calls model providers and costs money; it is priced and refused against your budget before anything starts. It does not act on the outside world a second time: connector steps are served from the baseline's recorded responses and agent steps keep only offline calculation tools. Returns the new run, not a comparison of it. Requires comparisons:write and workflows:run. 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.
run_comparison accepts 2 parameters: set_id, baseline_session_id. Required: set_id, baseline_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 run_comparison: 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.
run_comparison 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 run_comparison 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 run_comparison. 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.
run_comparison 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