> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usechar.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Governance Integrations

> Connect LangGuard or bring your own governance provider with the PDP interceptor contract.

<Note>
  **Private Beta** — [Contact us](mailto:alex@mcp-b.ai?subject=Enterprise%20Governance) to get set up.
</Note>

Char governance is integration-based. You choose the policy provider. Char handles tool execution orchestration and propagates provider decisions to runtime metadata and UI.

## Trust boundaries

* **IdP** provides authoritative identity, group, and role context.
* **Governance provider** provides authoritative policy outcomes.
* **UI hints and badges** are advisory only and should not be trusted for enterprise governance.

## Supported models

| Model            | Who owns policy logic | Integration path                    |
| ---------------- | --------------------- | ----------------------------------- |
| **LangGuard**    | LangGuard             | Configure interceptor URL + API key |
| **BYO Provider** | Your team or vendor   | Implement the interceptor contract  |

## Integration contract

Every provider must accept an `interceptor/validate` request and return:

* `success` to allow tool execution
* `notify` to allow execution with warnings
* `failure` to block execution

See [Policy Decision Point](/guides/governance/policy-decision-point) for the exact JSON-RPC request/response contract.

## Why this model

* You keep governance vendor choice and can switch providers later.
* Char does not require maintaining provider-specific policy engines.
* Tool-call policy outcomes remain portable through shared metadata.
* If no provider is configured or enabled, tool calls explicitly bypass governance checks.