# 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

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

## Facts

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

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `action` | string | yes |  |
| `reason` | string | no |  |
| `agent_id` | 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": "admin",
    "arguments": {
      "action": "<action>"
    }
  }
}
```

## Why admin is rated Low

All actions retrieve data or query state with no modifications, deletions, or external effects.

From the tool's own definition: "report abuse, get audit log, list templates, get votes, get vote state, replica pubkey"

Risk signals: Admin/system-level operation

## Use case

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.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "admin": {}
  }
}
```

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