label
label: 7 operations.
label: 7 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.
| Tool | label |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2, 1 required |
| Operation | POST /v1/risk/labels/dispose · POST /v1/risk/labels/hold · POST /v1/risk/labels · GET /v1/risk/labels/coverage · GET /v1/risk/labels/vocabulary · GET /v1/risk/labels · POST /v1/risk/labels/resolve |
| Product | risk |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
input | object | — | — | — | arguments for the chosen op |
op | string | yes | — | — | — |
tools/list declares a type, a description, which fields are required and an enumerated value set for each field and nothing further, and every column above is the door's own. This tool takes an operation name and that operation's arguments, so what the document constrains is what goes inside input, field by field, on the operation you name — ask describe for that. A — means the door does not constrain the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.
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": "label",
"arguments": {
"op": "<op>"
}
}
}'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
label dispatches to 7 operations.
| Operation | Route | Product | Summary |
|---|---|---|---|
riskDisposeLabels | POST /v1/risk/labels/dispose | risk | Dispose of this tenant's expired assertions, whole records only |
riskHoldLabels | POST /v1/risk/labels/hold | risk | Place or release a litigation hold on named records |
riskLabel | POST /v1/risk/labels | risk | Assert ground truth about events |
riskLabelCoverage | GET /v1/risk/labels/coverage | risk | How much of the window has matured, and how much of that is judged |
riskLabelVocabulary | GET /v1/risk/labels/vocabulary | risk | The closed vocabularies and the precedence rule that resolves a conflict |
riskLabels | GET /v1/risk/labels | risk | Read the assertions this tenant has recorded |
riskResolveLabels | POST /v1/risk/labels/resolve | risk | Resolve the label in force for named events, as of each event's own horizon |
The same capability over plain HTTP is in the risk API reference, on https://api.hanzo.ai.
How is this guide?