adminUpdateCap
Edits one cap by id — raise or lower the ceiling, flip enforcement.
Edits one cap by id — raise or lower the ceiling, flip enforcement. The body is commerce's spend-alert patch contract, forwarded byte-for-byte.
| Tool | adminUpdateCap |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2 |
| Operation | PATCH /v1/admin/caps/{id} |
| Product | cloud |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
id | string | — | — | — | ID is the cap to edit or remove, from the path. Unused by the list and create ops. |
org | string | — | — | — | Org is the tenant to act on. Required for a SuperAdmin — they must name their target; ignored for a white-label admin, who always acts on their own org. |
tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "adminUpdateCap",
"arguments": {
"id": "<id>",
"org": "<org>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
cloud_adminUpdateCap | PATCH /v1/admin/caps/{id} | cloud | Edits one cap by id — raise or lower the ceiling, flip enforcement. |
The same capability over plain HTTP is in the cloud API reference, on https://api.hanzo.ai.
All 833 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?