Guardian SDK settings and supported frameworks
Important Guardian Agents are available in private preview. Details in this topic are based on an early build and are subject to change before general availability.
The Collibra SDK is the Python package that attaches Guardian to an AI agent. This topic describes the SDK's settings, where it looks for the enforcement bundle, and the agent frameworks that it supports.
Where the SDK reads its settings
The SDK reads its settings from two places:
- The
collibra-guardian.tomlfile in the working directory of your program. The SDK doesn't search parent folders. - Environment variables named
COLLIBRA_GUARDIAN_<SETTING>, for exampleCOLLIBRA_GUARDIAN_ENFORCEMENT_MODE. They override the file. An empty variable counts as not set.
If you start your program with the CLI's run command, the SDK reads the settings in the same way. The CLI itself doesn't read them, and it doesn't pass any Collibra credentials to your program. The SDK warns about, and skips, any setting that it doesn't recognize.
Settings
| Setting | Default | Description |
|---|---|---|
enforcement_mode
|
enforce
|
enforce applies Guardian's verdicts. monitor records every decision but doesn't apply Deny, Escalate, or Rewrite. For details, go to Enforce and monitor modes. |
policy_bundle
|
bundle.zip in the working directory |
The path to the enforcement bundle. For details, go to Where the SDK finds the enforcement bundle. |
framework_version_policy
|
strict
|
strict stops the program before any of your agent's code runs when a framework version is outside the tested range. permissive only logs a warning. For the tested ranges, go to Supported frameworks. |
rule_engine, otel_endpoint_beta, otel_protocol_beta |
Not applicable | TBC - confirm whether to document these advanced settings. rule_engine names code that the SDK imports, so only run your program from a working directory that you trust. |
Where the SDK finds the enforcement bundle
The SDK looks for the enforcement bundle in the following places:
- The path in the
policy_bundlesetting. If that file doesn't exist, the program stops with a configuration error. - If the setting isn't set, the
bundle.zipfile in the working directory. This is the default file that the CLI's sync command writes, so run both commands from the same folder.
If the SDK finds no bundle, it isn't an error. Guardian allows every action, so nothing governs the agent. If logging is set up in your program, Guardian logs the warning guardian.no_policy_bundle. Otherwise, the program gives no sign that nothing is governed, so check that the bundle exists before you start.
Supported frameworks
Guardian supports the following versions of the AI agent frameworks. Install the SDK with the extras for the framework that your program uses.
| Framework | Tested versions | SDK extra |
|---|---|---|
| LangChain | 1.2 up to, but not including, 2.0 | guardian-langchain
|
| LangGraph | 1.1 up to, but not including, 2.0 | guardian-langgraph
|
| Deep Agents | 0.7 up to, but not including, 0.8 | guardian-deepagents
|
When you start a program with the CLI's run command, Guardian covers every agent that the program creates with LangChain's create_agent function, including Deep Agents, and the graphs that it compiles. It doesn't cover a LangGraph graph that you build by hand. For those, you need to add Guardian's model node and tool node wrappers to your code instead.