deliberate
Run an adversarial deliberation on a decision. Multiple AI perspectives argue opposing positions over multiple rounds, iteratively strengthening arguments, and converge on a recommendation with confidence scoring. Use for important decisions where you want to stress-test options from multiple ang...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/deliberate.md
What deliberate does on Freedom Mcp
AI agents invoke deliberate to trigger actions in Freedom Mcp. 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 |
|---|---|---|---|
run_id | string | — | Poll a background deliberation started earlier (MCP mode). Pass the run_id returned by the starting call, with the same companyId. Omit question/positions when |
context | string | — | Goals, constraints, values, and relevant data that should inform the deliberation. The more context, the better the arguments. |
criteria | array | — | Optional weighted evaluation criteria. Each item should have "name" (string) and "weight" (number 0-1, should sum to ~1). If omitted, defaults are generated. |
question | string | — | The decision or question to deliberate. Be specific — e.g., "Should we invest in mobile app development or API partnerships for growth in Q2?" Required unless p |
companyId | string | — | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
positions | array | — | Two or more positions to argue. Each should be a clear, distinct option — e.g., ["Mobile app development", "API partnerships", "Content marketing"]. Required un |
max_rounds | number | — | Maximum rounds of deliberation (default: 5). More rounds = better arguments but more compute. |
Parameters from the server's own tool schema.
Why deliberate is rated High
While the tool does not modify data directly (ruling out Write/Destructive) nor move money (ruling out Financial), it executes a complex external operation—spawning background deliberation processes with AI agents that analyze and influence decision-making.
From the tool's definition "Run an adversarial deliberation on a decision" and "call deliberate again with { run_id }" indicate the tool executes a background computational process that performs analysis and generates recommendations based on decision inputs.
Attacks that exploit this kind of access
The rule that runs deliberate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deliberate, this is the rule to start with:
deliberate 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 Freedom Mcp, apply this rule, and every deliberate call is checked against it from then on.
Questions about deliberate
Run an adversarial deliberation on a decision. Multiple AI perspectives argue opposing positions over multiple rounds, iteratively strengthening arguments, and converge on a recommendation with confidence scoring. Use for important decisions where you want to stress-test options from multiple angles. Over MCP the deliberation runs in the background: the first call returns a run_id immediately; call deliberate again with { run_id } (plus the same companyId) after ~1-2 minutes to fetch the result. Routing: Important decision → deliberate for adversarial analysis. It is categorised as a Execute tool in the Freedom Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
deliberate accepts 7 parameters: run_id, context, criteria, question, companyId, positions, max_rounds. The full parameter table on this page comes from the server's own tool schema.
Register the Freedom MCP server in PolicyLayer and add a rule for deliberate: 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 Freedom Mcp. Nothing to install.
deliberate 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 deliberate 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 deliberate. 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.
deliberate is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freedom, and thousands of servers like it.
Across the catalogue