Critical Risk →

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) - publish_position: Publish a draft position (position_id) - vote: Vote...

Risk signalsAccepts raw HTML/template content (content) · High parameter count (23 properties)

Part of the Gemot Deliberation Server server.

participate can permanently delete data in Gemot Deliberation Server, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE GEMOT DELIBERATION SERVER →

Free to start. No card required.

AI agents may call participate to permanently remove or destroy resources in Gemot Deliberation Server. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call participate in a loop, permanently destroying resources in Gemot Deliberation Server. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "participate"
  ]
}

See the full Gemot Deliberation Server policy for all 6 tools.

Get this rule live on your own Gemot Deliberation Server server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY GEMOT DELIBERATION SERVER →

These attack patterns abuse exactly the kind of access participate gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so participate only ever does what you allow.

SECURE GEMOT DELIBERATION SERVER →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the participate tool do? +

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

How do I enforce a policy on participate? +

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.

What risk level is participate? +

participate is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit participate? +

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.

How do I block participate completely? +

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.

What MCP server provides participate? +

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.

Enforce policy on every Gemot Deliberation Server tool call.

Deterministic rules across all 6 Gemot Deliberation Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.