get_v1_connectors_id_token
Hands the custodied access token to its owner — the ONE place custody exits. The (org,user)-keyed row IS the same-user gate: another user's id is simply "no row" → 404.
Hands the custodied access token to its owner — the ONE place custody exits. The (org,user)-keyed row IS the same-user gate: another user's id is simply "no row" → 404. fresh() auto-rotates within the refreshSkew window; static providers degenerate to a plain kmsGet of Secrets[0]. Refresh tokens are NEVER returned — custody keeps the sink. The token is never logged.
| Tool | get_v1_connectors_id_token |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 1, 1 required |
| Operation | GET /v1/connectors/{id}/token |
| Product | connectors |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
id | string | yes | — | — | ID is the connector id, provider + ":" + label ("openai:default") — the auth-profile-id shape. Another user's id is simply no row, so 404. |
tools/list declares a type and a description for each field and nothing further. The Required column is taken from GET /v1/connectors/{id}/token, the operation this tool dispatches to — the same declaration the REST API validates against. 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. 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": "get_v1_connectors_id_token",
"arguments": {
"id": "<id>"
}
}
}'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 |
|---|---|---|---|
get_v1_connectors_id_token | GET /v1/connectors/{id}/token | connectors | Hands the custodied access token to its owner — the ONE place custody exits. |
The same capability over plain HTTP is in the connectors API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?