Update an MCP Server
Change a server’s upstream, tool allowlist, PII inspection or auth mode.
upstream_url is
re-validated through the SSRF chokepoint, a literal credential in auth.headers
is refused, and userinfo in the URL (https://user:pass@host/) is rejected — a
credential written into a URL lands in plaintext in every log line and error
message that echoes it.
Setting allowed_tools to [] takes every tool off the server. That is a valid
thing to want and it is not a soft state: the server will advertise nothing.
Requires the update capability on ai_gateway. See the control-plane overview for authentication, the {data, meta} envelope, pagination and error types.Authorizations
OAuth 2.1 authentication — recommended for new integrations. Access tokens
(kc_ prefix) are minted at the root-host token endpoint
https://api.knoxcall.com/oauth/token and passed as Authorization: Bearer <access_token>.
Public clients must use PKCE with the authorization_code grant; confidential
clients may use client_credentials. The first-party SDKs and the
knoxcall login CLI handle token minting, caching, refresh, and DPoP for you.
Path Parameters
The MCP server UUID.
Body
Only streamable_http is accepted (see the create request).
streamable_http Upstream auth for an MCP server. A secret reference is the only supported path: every header value must contain a {{secret_id:<uuid>}} (or legacy {{secret:<name>}}) placeholder. A literal is refused with 422 plaintext_auth — it would sit in cleartext in the control plane.
Use DELETE to archive.
active, paused A PII policy THIS tenant owns (AIGW-151). A policy id you do not own is refused 422 — the FK is id-only, so the ownership check is the control.
https only; no embedded credentials; SSRF-checked at write time.
off, request, response, both 100 <= x <= 10000fail_open, fail_closed