An agent hitting a live Databricks backend stays inside policy controls
Recorded on 4.11, now 4.13Customer safe
Say while it plays
The same hotel concierge agent and live Databricks backend run both with the gateway dropped out and with it in place, so you can toggle governance on and off against identical traffic rather than comparing two different builds.
With the gateway in, an over-reaching 'delete my booking' request and a 'leak personal information' request both get refused by policy, and a 2,000-token transcript dropped in as a prompt gets rejected before it ever reaches the model.
A risky action escalates to a human-in-the-loop approval step logged to OpenTelemetry, and with the gateway off that same identity's prompt returns every member's data instead of just the caller's own bookings.
Chapters
Introduction and purpose of the demo
Architecture overview – live Databricks backend and LLM routing
New UI wrapper and gateway toggle functionality
Gateway‑enabled policy enforcement and permission checks