# account

Fund your gemot credit balance. Actions: - buy_credits: Top up THIS API key's balance over the ATXP/x402 rail (optional: pack, atxp_account_id, payment_credential). Call once with no payment_credential to receive a payment-required challenge (the x402 accepts to pay against), then call again with payment_credential set to the base64 X-PAYMENT settle credential. Credits are added only on a settled, on-chain-confirmed charge.

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

## Facts

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

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `pack` | string | no |  |
| `action` | string | yes |  |
| `atxp_account_id` | string | no |  |
| `payment_credential` | 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": "account",
    "arguments": {
      "action": "<action>"
    }
  }
}
```

## Why account is rated Critical

Tool initiates and settles on-chain financial payments to top up account credits.

From the tool's own definition: "Fund your gemot credit balance, buy_credits, on-chain-confirmed charge"

## Use case

AI agents use account to commit financial operations through Gemot Deliberation Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "account": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}
```

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