The parts
Bridge doesn’t govern anything on its own. It routes each client through your Barndoor organization, and the organization’s settings hold the rules.
Model traffic
1
The client sends its requests to Bridge
A governed client sends its model requests to Bridge on the same laptop, never directly to Anthropic or OpenAI.
2
Bridge forwards them to the LLM Gateway
Bridge forwards only to your organization’s Barndoor LLM Gateway. Each session uses a short-lived Barndoor credential, tied to the person and the client, that Bridge renews about once an hour and revokes when the client exits. The credential can reach only the models the person is allowed.
3
The gateway applies your rules
Model Access decides which models the request may use. Data protection runs on the request and the response. The call is audited with the person, the client, and the agent.
4
The gateway calls the provider
The Model Route decides where the request goes: Anthropic, OpenAI, Amazon Bedrock, Google Vertex AI, or another configured provider.
Tool traffic
Every governed client gets exactly one MCP server, Barndoor (none when Bridge governs models only; under MCP only, a person’s own Claude Desktop keeps its other servers too). It gives the agent a small set of tools for finding and calling everything else. Behind it are:
Policy is checked on every call, at call time. For tools that run on the laptop, Bridge asks Barndoor before running anything. If Barndoor can’t be reached, Bridge falls back to a signed copy of the policy for the tools the session has already used, for up to 24 hours. Any other tool is refused.
Approvals come from your organization’s policy in the Access Control Center. A tool set to Needs Approval pauses until the person approves the call; a tool set to Always Allow runs; a tool the policy doesn’t grant is refused. Approval is per call: the person sees exactly what will run, with its arguments, and approves that call only. Apart from Bridge’s own bundled skills and utilities, which ask before a destructive action, Bridge adds no approval rules of its own. See Tool confirmations.
Data protection applies to every tool call, wherever the tool runs. Remote MCP servers are scanned on the Barndoor platform as their calls pass through it. For a tool that runs on the laptop, Bridge sends the tool’s input to Barndoor for scanning before the tool runs, and its output before the client sees it, then applies the verdict: allow, redact or tokenize (the tool or the client gets the rewritten text), or block. Scanning happens on the platform, not the laptop, so verdicts, wording, and audit match remote calls.
- Only your organization’s data protection policies act. With none for a server, nothing is sent for scanning.
- It fails closed. If a call can’t be scanned, for example because Barndoor is unreachable, the call is refused or its output withheld rather than delivered unscanned. The one exception: if Barndoor is unreachable and your organization had no data protection policies when Bridge last checked, in the past 24 hours, local calls run unscanned.
- A skill’s steps are checked and scanned one tool at a time, and a block stops the skill.
- Bridge’s own helpers, such as memory across sessions and session history, aren’t checked against policy or scanned. They don’t reach outside Bridge.
- Field controls aren’t evaluated on local servers. If you set one on a local server, that server’s calls are withheld.
shell/shell_exec. The audit record names the tool and the policy decision, not the command. When a data protection policy covers the Shell server, the command is also scanned before it runs. Admins can also block commands outright with client settings.
Organization-published local MCP servers
A local MCP server your organization publishes runs only if three independent parties agree:
Bridge checks the signature against the pinned key, downloads the build only from an allowed host, checks its SHA-256, and checks it again on every launch. If any check fails, the server doesn’t run. See Publish a local MCP server.
What Bridge governs
Everything above assumes Bridge governs models and MCP, the default. Admins can instead choose models only, where the model path applies and Bridge adds no Barndoor MCP server, or MCP only, where the tool path applies and models run on each person’s own Claude or OpenAI sign-in, outside the LLM Gateway. See Choose what Bridge governs, and Govern tools only (MCP only) for what that mode guarantees.What every governed session has
The client’s own built-in tools (file edits, shell, web fetch, browser) run on the laptop and don’t go through Barndoor’s tool policy. Admins decide which of them stay on with client settings; by default every one is on, exactly as the client ships. Barndoor’s own tools work the other way: they are denied by default, and a tool runs only when a policy grants it. Whatever the client settings say, every session has these properties when Bridge governs Models and MCP or Models only. Under MCP only, models and the client’s own tools aren’t governed, and the list is different; see Govern tools only (MCP only).- Model traffic goes only to the LLM Gateway.
- Barndoor is the only MCP server. MCP servers the person configured locally, and plugins’ MCP servers, don’t connect. Two exceptions: Claude Desktop still runs servers from plugins your administrators deploy to its organization plugins folder, and under Models only, where Bridge adds no MCP server, Claude Code can load a project’s own
.mcp.jsonservers once the person approves each one. - The person can’t widen the settings from the command line.
- Usage and audit records carry the client settings version: the one at launch, then the current one after each hourly renewal.
- Launches fail closed. If the installed client isn’t a version Barndoor supports (unless you allow unreviewed Codex Desktop versions), a workspace carries a competing configuration, or the person is allowed no model the client can use, Bridge refuses to launch rather than start the client ungoverned.
What Barndoor sees
Barndoor doesn’t see what the client’s own built-in tools do on the laptop (a native shell command, a native file edit, a native web fetch) except where it shows up in the conversation sent to the model. It doesn’t read files on the laptop except through a tool call.
What Bridge doesn’t do
Bridge governs the sessions it launches. On its own it doesn’t stop someone opening Claude, ChatGPT, or another AI tool directly. The Codex policy, on by default, makes Codex run only through Barndoor; provider lockdown, off by default, blocks direct access to provider APIs and does the same for Claude. Sign-ins stored on the laptop, such as a Claude or ChatGPT sign-in, stay readable by the person who owns the account on that machine.What each control covers
Each row is something a person could otherwise do, and the control that covers it. The defaults are for Models and MCP.Install and update integrity
- macOS: a signed, notarized installer (
Developer ID Installer: Barndoor AI, Inc., team547SWHX99F). The MDM updater accepts packages only fromdownloads.barndoor.ai, checks the SHA-256, the package signature, and Gatekeeper, and never downgrades. - Windows: an MSI installer, with the MSI and both programs code-signed by Barndoor AI, Inc. See Install on Windows.
- Version control belongs to IT. On a managed machine, Bridge refuses to update itself; IT’s MDM decides the version.