admin
Admin and audit tools. Actions: - report_abuse: Report abusive content (deliberation_id, reason) - get_audit_log: Get audit trail incl. tamper-evident log with proofs (deliberation_id) - list_templates: List available governance templates - get_votes: Get all votes (deliberation_id) - get_vote_st...
This record as markdown: /tools/dev-gemot-gemot/admin.md
What admin does on Gemot Deliberation Server
AI agents call admin to retrieve information from Gemot Deliberation Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | Yes | |
reason | string | — | |
agent_id | string | — | |
deliberation_id | string | — |
Parameters from the server's own tool schema.
Why admin is rated Low
All actions retrieve data or query state with no modifications, deletions, or external effects.
From the tool's definition report abuse, get audit log, list templates, get votes, get vote state, replica pubkey
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs admin 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 admin, this is the rule to start with:
admin is read-only, so it stays allowed. 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 admin call is checked against it from then on.
Questions about admin
Admin and audit tools. Actions: - report_abuse: Report abusive content (deliberation_id, reason) - get_audit_log: Get audit trail incl. tamper-evident log with proofs (deliberation_id) - list_templates: List available governance templates - get_votes: Get all votes (deliberation_id) - get_vote_state: Get your own agent's recorded votes to confirm they landed and whether each is marked relayed vs direct (deliberation_id, agent_id) - replica_pubkey: Get the server's BLS public key for offline proof verification. It is categorised as a Read tool in the Gemot Deliberation Server MCP Server, which means it retrieves data without modifying state.
admin accepts 4 parameters: action, reason, agent_id, 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 admin: 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.
admin is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the admin 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 admin. 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.
admin 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