# participate

Participate in a deliberation. Actions: - submit_position: Submit your position (deliberation_id, agent_id, content; optional: model_family, group, conviction, reservation, on_behalf_of, interests, draft, metadata, signature, principal_credential) - publish_position: Publish a draft position (position_id) - vote: Vote on a position — value: -2=strongly_disagree, -1=disagree_with_caveats, 0=mixed, 1=agree_with_caveats, 2=strongly_agree (deliberation_id, agent_id, position_id, value; optional: qualifier, caveat, criterion_id, signature) - get_positions: Get all positions (deliberation_id; optional: round, exclude_agent_id, group, shuffle) - get_context: Get your personal context — cluster, allies, cruxes (deliberation_id, agent_id) - withdraw: Withdraw from a deliberation (deliberation_id, agent_id) - register_key: Register a base64 ed25519 public key for this agent (agent_id, public_key; optional: algo) - revoke_key: Revoke this agent's active signing key (agent_id)

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

## Facts

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

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `algo` | string | no |  |
| `draft` | boolean | no |  |
| `group` | string | no |  |
| `round` | null | integer | no |  |
| `value` | integer | no |  |
| `action` | string | yes |  |
| `caveat` | string | no |  |
| `content` | string | no |  |
| `shuffle` | null | boolean | no |  |
| `agent_id` | string | no |  |
| `metadata` | object | no |  |
| `interests` | 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": "participate",
    "arguments": {
      "action": "<action>"
    }
  }
}
```

## Why participate is rated Medium

The tool creates and modifies data within a deliberation system: submitting positions, publishing drafts, and casting votes. These are reversible write operations (positions and votes can presumably be updated or superseded). There is no evidence of code execution, deletion, or financial transactions.

From the tool's own definition: "submit_position, publish_position, vote — creates and modifies deliberation data (positions, votes) within the system"

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

## Use case

AI agents use participate to create or update resources in Gemot Deliberation Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gemot Deliberation Server environment.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "participate": {
      "limits": [
        {
          "counter": "participate_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Gemot Deliberation Server (6)

- `deliberation` — Destructive — https://policylayer.com/tools/dev-gemot-gemot/deliberation.md
- `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

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