The publish workflow
- Edit your policies in the console (these are drafts)
- Publish a release from the Releases tab — this snapshots your current policies and makes it the active release
Create a release
Review your policies
Go to Policies and review all your policy rules. Make sure the expressions, effects (allow/deny), and ordering are correct.
Version management
Every release gets a version number. You can:- View any past release to see what policies were active at that time
- Rollback to a previous release if something goes wrong
- Compare releases to see what changed
How the gateway uses releases
When you publish a new release, it becomes the active release. The gateway picks up changes within about a minute. There’s no downtime — in-flight requests complete with the old policies, and new requests use the updated ones.No release published
If no release has been published for a project, the gateway uses the project’s default policy action:- Deny (recommended) — all tool calls are blocked
- Allow — all tool calls are permitted
Next steps
View executions
Check the audit log to verify policies are working as expected.
Policy examples
Real-world policy patterns to reference.