add_comparison_runs
Append finished runs you own to a set. All or nothing: a run that is unknown, not yours, still running, or already a member refuses the whole call and leaves the set exactly as it was. Requires comparisons:write.
This record as markdown: /tools/com-meta-council-decision-intelligence/add-comparison-runs.md
What add_comparison_runs does on Meta Council
AI agents use add_comparison_runs to create or update resources in Meta Council, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Council environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
set_id | string | Yes | |
session_ids | array | Yes |
Parameters from the server's own tool schema.
Why add_comparison_runs is rated Medium
An AI agent can call add_comparison_runs faster than any human can review: one bad instruction and it creates or modifies resources in Meta Council by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs add_comparison_runs 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 add_comparison_runs, this is the rule to start with:
add_comparison_runs stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 add_comparison_runs call is checked against it from then on.
Questions about add_comparison_runs
Append finished runs you own to a set. All or nothing: a run that is unknown, not yours, still running, or already a member refuses the whole call and leaves the set exactly as it was. Requires comparisons:write. It is categorised as a Write tool in the Meta Council MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
add_comparison_runs accepts 2 parameters: set_id, session_ids. Required: set_id, session_ids. 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 add_comparison_runs: 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.
add_comparison_runs is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_comparison_runs 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 add_comparison_runs. 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.
add_comparison_runs 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