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 (pos...
This record as markdown: /tools/dev-gemot-gemot/participate.md
What participate does on Gemot Deliberation Server
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
algo | string | — | |
draft | boolean | — | |
group | string | — | |
round | null | integer | — | |
value | integer | — | |
action | string | Yes | |
caveat | string | — | |
content | string | — | |
shuffle | null | boolean | — | |
agent_id | string | — | |
metadata | object | — | |
interests | string | — |
Parameters from the server's own tool schema.
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 definition submit_position, publish_position, vote — creates and modifies deliberation data (positions, votes) within the system
Risk signalsAccepts raw HTML/template content (content) · High parameter count (24 properties)
Attacks that exploit this kind of access
The rule that runs participate 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 participate, this is the rule to start with:
participate 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 Gemot Deliberation Server, apply this rule, and every participate call is checked against it from then on.
Questions about 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). It is categorised as a Write tool in the Gemot Deliberation Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
participate accepts 12 parameters: algo, draft, group, round, value, action, caveat, content, shuffle, agent_id, metadata, interests. 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 participate: 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.
participate 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 participate 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 participate. 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.
participate 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.
This server
Across the catalogue