# 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)

Agent View of the PolicyLayer registry record for `deliberation`. HTML page: https://policylayer.com/tools/dev-gemot-gemot/deliberation

## Facts

- Tool: `deliberation`
- Server: Gemot Deliberation Server (`https://gemot.dev/mcp`) — https://policylayer.com/tools/dev-gemot-gemot.md
- Homepage: https://github.com/justinstimatze/gemot
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 12 (1 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `type` | string | no |  |
| `limit` | integer | no |  |
| `rules` | object | no |  |
| `topic` | string | no |  |
| `action` | string | yes |  |
| `offset` | integer | no |  |
| `agent_id` | string | no |  |
| `group_id` | string | no |  |
| `template` | string | no |  |
| `visibility` | string | no |  |
| `description` | string | no |  |
| `deliberation_id` | string | no |  |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "deliberation",
    "arguments": {
      "action": "<action>"
    }
  }
}
```

## 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 own definition: "'delete: Soft-delete a deliberation (deliberation_id)' — the tool explicitly supports deletion of deliberations, even if described as 'soft-delete'."

Risk signals: Accepts raw HTML/template content (template) · High parameter count (16 properties)

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Gemot Deliberation Server:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "deliberation"
  ]
}
```

## Other tools on Gemot Deliberation Server (6)

- `analyze` — Execute — https://policylayer.com/tools/dev-gemot-gemot/analyze.md
- `account` — Financial — https://policylayer.com/tools/dev-gemot-gemot/account.md
- `admin` — Read — https://policylayer.com/tools/dev-gemot-gemot/admin.md
- `decide` — Read — https://policylayer.com/tools/dev-gemot-gemot/decide.md
- `coordinate` — Write — https://policylayer.com/tools/dev-gemot-gemot/coordinate.md
- `participate` — Write — https://policylayer.com/tools/dev-gemot-gemot/participate.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-gemot-gemot · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-gemot-gemot