deliberation
Manage deliberations. Actions: - create: Create a new deliberation (topic, description, template, group_id, deadline_minutes, rules, visibility, max_participants, type, principal_policy, signature_policy) - get: Get status/stats of a deliberation (deliberation_id) - list: List all deliberations (...
This record as markdown: /tools/dev-gemot-gemot/deliberation.md
What deliberation does on Gemot Deliberation Server
AI agents call deliberation to permanently remove resources in Gemot Deliberation Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | |
limit | integer | — | |
rules | object | — | |
topic | string | — | |
action | string | Yes | |
offset | integer | — | |
agent_id | string | — | |
group_id | string | — | |
template | string | — | |
visibility | string | — | |
description | string | — | |
deliberation_id | string | — |
Parameters from the server's own tool schema.
Why deliberation is rated Critical
The tool spans Read (get, list), Write (create, set_template), and Destructive (delete) actions. Per the rules, the most severe applicable category wins. The delete action ('Soft-delete a deliberation') makes this Destructive. Severity is high because deliberations represent multi-agent coordination state — deleting one could disrupt consensus processes, lose crux/vote data, and affect all participating agents.
From the tool's definition 'delete: Soft-delete a deliberation (deliberation_id)' — the tool explicitly supports deletion of deliberations, even if described as 'soft-delete'.
Risk signalsAccepts raw HTML/template content (template) · High parameter count (16 properties)
Attacks that exploit this kind of access
The rule that runs deliberation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gemot Deliberation Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deliberation, this is the rule to start with:
deliberation is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Gemot Deliberation Server, apply this rule, and every deliberation call is checked against it from then on.
Questions about deliberation
Manage deliberations. Actions: - create: Create a new deliberation (topic, description, template, group_id, deadline_minutes, rules, visibility, max_participants, type, principal_policy, signature_policy) - get: Get status/stats of a deliberation (deliberation_id) - list: List all deliberations (limit, offset) - list_by_group: List deliberations in a group (group_id, limit, offset) - list_by_agent: List deliberations an agent participated in (agent_id, limit, offset) - delete: Soft-delete a deliberation (deliberation_id) - set_template: Change governance template (deliberation_id, template) - export: Export complete multi-round history (deliberation_id). It is categorised as a Destructive tool in the Gemot Deliberation Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
deliberation accepts 12 parameters: type, limit, rules, topic, action, offset, agent_id, group_id, template, visibility, description, deliberation_id. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Gemot Deliberation Server MCP server in PolicyLayer and add a rule for deliberation: 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 Gemot Deliberation Server. Nothing to install.
deliberation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deliberation 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 deliberation. 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.
deliberation is provided by the Gemot Deliberation Server MCP server (https://gemot.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gemot Deliberation Server, and thousands of servers like it.
Across the catalogue