put_v1_ingress_middlewares_id
PutMiddleware creates or replaces one edge transform and hot-applies it. POST mints an id when the body omits one; PUT takes the id from the URL, which wins over any id in the body.
PutMiddleware creates or replaces one edge transform and hot-applies it. POST mints an id when the body omits one; PUT takes the id from the URL, which wins over any id in the body. type must be one of redirectScheme, stripPrefix, addPrefix or headers, and stripPrefix/addPrefix each require their config key.
| Tool | put_v1_ingress_middlewares_id |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 3 |
| Operation | PUT /v1/ingress/middlewares/{id} |
| Product | ingress |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
config | object | — | — | — | Config is the transform's parameters: redirectScheme takes scheme (default https) and permanent ("true" ⇒ 301, else 302); stripPrefix REQUIRES prefixes (comma-separated, first match wins); addPrefix REQUIRES prefix; headers is a header→value map set on the response. |
id | string | — | — | — | ID identifies the transform within the org: [A-Za-z0-9-_.], at most 128 chars. A create that omits it gets a generated one. Routes reference it by this id. |
type | string | — | — | — | Type is the transform: redirectScheme, stripPrefix, addPrefix or headers. |
tools/list declares a type and a description for each field and nothing further. 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. Nothing above is required, so every declared argument is shown rather than a guess at which matter.
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": "put_v1_ingress_middlewares_id",
"arguments": {
"config": {},
"id": "<id>",
"type": "<type>"
}
}
}'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 |
|---|---|---|---|
put_v1_ingress_middlewares_id | PUT /v1/ingress/middlewares/{id} | ingress | Creates or replaces one edge transform and hot-applies it. |
The same capability over plain HTTP is in the ingress 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?
post_v1_ingress_services
PutService creates or replaces one backend pool and hot-applies it. POST mints an id when the body omits one; PUT takes the id from the URL, which wins over any id in the body.
put_v1_ingress_routes_id
PutRoute creates or replaces one routing rule and hot-applies the new table — there is no config file and no restart.