Skip to main content
PATCH
Update a prompt-firewall policy
Partial update. Omitted fields are left as they are. Changing action to block takes effect on every agent that references this policy, on their next request. Dry-run the rule set with Test firewall rules first — under block, a rule that will not compile stops being a warning and becomes a 503 on live traffic. Requires the update capability on ai_gateway. See the control-plane overview for authentication, the {data, meta} envelope, pagination and error types.

Authorizations

Authorization
string
header
required

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

id
string<uuid>
required

Body

application/json
heuristics
object[]
canary_enabled
boolean
action
enum<string>
Available options:
block,
warn,
tag

Response

The updated policy.

data
object

A tenant-scoped prompt-firewall policy, attachable to agents and MCP servers.

meta
object

Metadata included with every API response.