delete_v1_cloud_provider_accounts_label
Forgets one linked cloud account: it detaches every fleet cluster THIS account folded (its own names, in its own shard — a neighbour's cluster of the same name is untouched), deletes the sealed…
Forgets one linked cloud account: it detaches every fleet cluster THIS account folded (its own names, in its own shard — a neighbour's cluster of the same name is untouched), deletes the sealed credential, and drops the index row.
It is idempotent and deliberately not an existence oracle: an account this org does not hold answers exactly the same as one it just removed. A cluster that fails to detach is logged and the unlink continues, so a dead provider cannot strand a credential. Requires org admin.
| Tool | delete_v1_cloud_provider_accounts_label |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2, 2 required |
| Operation | DELETE /v1/cloud/{provider}/accounts/{label} |
| Product | cloud |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
label | string | yes | — | — | Label is the org-chosen name of the account within that provider. Empty means "default"; anything outside 1–64 of [A-Za-z0-9._-] is refused. |
provider | string | yes | — | — | Provider is the cloud the account belongs to: digitalocean, aws, gcp or azure. An unknown provider is not found. |
tools/list declares a type and a description for each field and nothing further. The Required column is taken from DELETE /v1/cloud/{provider}/accounts/{label}, 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": "delete_v1_cloud_provider_accounts_label",
"arguments": {
"label": "<label>",
"provider": "<provider>"
}
}
}'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 |
|---|---|---|---|
delete_v1_cloud_provider_accounts_label | DELETE /v1/cloud/{provider}/accounts/{label} | cloud | Forgets one linked cloud account: it detaches every fleet cluster THIS account folded… |
The same capability over plain HTTP is in the cloud 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?