settings
2 MCP tools on the Hanzo cloud door that call the settings API.
The 2 tools tools/list names for settings. Each dispatches to an operation in the settings API reference.
| Tool | Route | Arguments | Required | Description |
|---|---|---|---|---|
get_v1_settings_product | GET /v1/settings/{product} | 1 | product | GetSettings reads the caller org's configuration for one product, with every secret field MASKED —… |
put_v1_settings_product | PUT /v1/settings/{product} | 3 | — | PutSettings writes the caller org's configuration for one product and answers the stored result,… |
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?
post_v1_sbom
Ingest persists a CycloneDX SBOM's components keyed by image digest. Gated to a validated SuperAdmin (owner == AdminOrg) — the canonical cloud super-admin check, which the build fleet / CI carries.
get_v1_settings_product
GetSettings reads the caller org's configuration for one product, with every secret field MASKED — only the names of the set secrets come back, never their values, which live in KMS.