adminSetFlag
Stores or overwrites ONE platform switch's definition and answers with the whole board as it now stands.
Stores or overwrites ONE platform switch's definition and answers with the whole board as it now stands. The flip is hot: this pod applies it immediately and peers converge within one evaluation TTL (15s by default), with no redeploy.
The body reaches the flag engine BYTE-FOR-BYTE — it is the engine's definition format, not this layer's, so a field the engine understands and admin does not must still arrive intact. setFlagIn names the two fields that matter for documentation; it is not a filter.
The write is recorded in the store's activity log against the caller's email.
| Tool | adminSetFlag |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 3 |
| Operation | PUT /v1/admin/flags/{key} |
| Product | cloud |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
active | boolean | — | — | Active is the switch itself: true enables the flag for every evaluation. |
filters | any | — | — | Filters is the optional rollout/payload block of a VALUED switch, e.g. {"groups":[{"properties":[],"rollout_percentage":100}],"payloads":{"true":250}}. |
key | string | — | — | Key is the switch to write, taken from the path (e.g. "waitlist.chat"). |
This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.
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": "adminSetFlag",
"arguments": {
"active": false,
"filters": "<filters>",
"key": "<key>"
}
}
}'Values are placeholders derived from each field's declared type. 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_adminSetFlag | PUT /v1/admin/flags/{key} | cloud | Stores or overwrites ONE platform switch's definition and answers with the whole board as |
The same capability over plain HTTP is in the cloud API reference, on https://api.hanzo.ai.
All 834 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?