Reset the cluster default guardrails
Delete the saved cluster default so the built-in default applies again: switched on, with prompt injection and leakage detection. To stop enforcing a cluster default, update it with enabled set to false instead.
Authorizations
Gateway auth: send Authorization: Bearer <mka1-api-key>. For multi-user server-side integrations, you can also send X-On-Behalf-Of: <external-user-id>.
Response
OK
Cluster switch. When false, the cluster default applies to no organization.
Guardrails enforced on every enrolled organization
Banned words guardrail
- Option 1
- Option 2
- Option 3
- Option 4
True while the cluster runs the built-in default (prompt injection and leakage detection) because no operator has saved one
True when the saved cluster default cannot be read: the built-in rules shown here are enforced in its place. Save a policy to replace it; do not save these rules back unless that is intended
User who last changed the cluster default; null while the built-in default applies
When the cluster default was last changed; null while the built-in default applies