SYSTEM Cited by 1 source
Omnigent¶
Omnigent is Databricks' open-source AI agent framework, notable for its built-in contextual policy engine that evaluates every tool call against multiple policy layers before allowing execution.
Architecture¶
The framework runs a single policy engine per session that evaluates tool calls against a stack of contextual policies. Each policy returns one of three verdicts:
- ALLOW — action proceeds.
- ASK — action is paused for human approval.
- DENY — action is blocked.
Policies compose with deny-wins semantics: if any single policy denies an action, it is blocked regardless of what other policies say. This makes the policy set monotonically restrictive — adding a new permissive policy cannot override an existing denial.
Built-in policy types¶
- Intent-based authorization — binds a session to a declared purpose; any tool call outside that purpose is denied or gated (patterns/intent-based-authorization).
- Session-risk scoring — behavioral anomaly detection that tracks drift from expected session patterns (described in companion blog "Blocking Slow-Burn Attacks").
- PII blocking — prevents exposure of sensitive data in agent outputs.
- Custom rules — user-defined policies in plain language, compiled to enforceable rules.
Key design decisions¶
-
Intent is immutable at runtime. For autonomous agents, intent is pinned in the agent spec. For interactive agents, intent is set at session start with human approval. The running agent has no tool to edit, remove, or disable policies.
-
Adding policies requires human approval. Even if an agent has a "add policy" tool, a built-in meta-rule gates new policy activation on explicit user consent.
-
Deny-wins composition prevents policy escalation — a new permissive rule cannot lift an existing block (patterns/deny-wins-policy-composition).
Status¶
Open source, in alpha as of July 2026. Documentation at omnigent.ai/docs.
Seen in¶
- sources/2026-07-23-databricks-intent-based-authorization-omnigent — introduces intent-based authorization as a contextual policy, demonstrates blocking indirect prompt injection that exploits identity-permission gap.
Related¶
- concepts/intent-based-authorization — the core concept
- concepts/prompt-injection — the attack class Omnigent's policies mitigate
- patterns/deny-wins-policy-composition — key policy-combination semantic
- patterns/minimally-scoped-llm-tools — static tool scoping (complementary approach)
- concepts/least-privileged-access — least privilege at identity layer; Omnigent adds least privilege at intent layer