Skip to main content
Private BetaContact us to get set up.
Some deployments need more than tool access—they need controls. Who can use which tools, from where, under what conditions. What gets inspected. What requires approval. What gets logged. Char is provider-agnostic. You plug in your governance platform (LangGuard or BYO interceptor), and Char enforces its decisions uniformly across embedded agents, remote MCP servers, the browser extension, and autonomous execution.

Authority model

  • Identity provider (IdP) is authoritative for identity, groups, and roles.
  • Governance provider is authoritative for tool policy decisions (success, notify, failure).
  • Char UI hints are informational only and are not enterprise enforcement controls.
  • No managed policy engine is required from Char for custom governance logic.

Decision flow

Every tool call flows through multiple layers: Identity context determines who is calling and what role context is attached. Policy provider evaluates content and context—is there PII in the arguments, does this look like prompt injection, does it violate org policies. Approval checks the risk classification—read-only operations auto-approve, destructive operations require explicit sign-off. Audit logs everything—who did what, when, with what arguments, what the result was.

In this section