Browserbase MCP server and Dome
Give agents a real browser, and decide where it goes. Browserbase runs cloud browsers that agents drive with Stagehand: navigate, act, observe and extract. Connect its hosted MCP server to Dome once, and rules decide every navigation on its URL. Every session, page and action lands in one audit trail.
Dome provides a governed gatewayfor Browserbase.
Every navigation decided
Rules read the URL of each navigate call. A carrier portal on the list opens, and a lookalike domain is refused.
One list per agent
Each agent's sites live in its own rule bundle. The release checker reaches staging, and a wider list for another agent doesn't touch it.
Each step on the record
Sessions, pages, clicks and extractions are each a tool call. The audit trail shows what the agent did, in order.
Browserbase behind the Gatewayin three steps.
Add the Browserbase server, sync its six tools, then give each agent its list of sites.
Add the Browserbase MCP server
Dome keeps the Browserbase API key and sends it as a Bearer token. Sessions run on your Browserbase account.
shelldome tools add --name browserbase \ --url https://mcp.browserbase.com/mcp \ --auth-method api-key \ --credential-type shared \ --authorization "Bearer $BROWSERBASE_API_KEY" \ --gateway prod-gatewaySync the catalog
Browserbase lists its six tools without a session. The key is spent only when an agent calls one.
shelldome tools catalog sync browserbaseApply the rules
The portal list is scoped to shipment-tracker. Simulate a lookalike domain, then deploy.
shelldome rules apply browserbase-permit.cedar browserbase-sites.cedar \ --agent shipment-tracker --name browserbase-sites
Browse two carrierportals, nothing else.
The permit opens the session tools to the agent. The forbid refuses any navigation whose URL isn't on one of two carrier portals, including lookalike domains and plain http.
cedar
permit (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "browserbase" && ["start", "navigate", "observe", "extract", "act", "end"].contains(resource.tool_name)};
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "browserbase" && resource.tool_name == "navigate" && !(resource has arguments && resource.arguments has url && (resource.arguments.url like "https://carrier.meridian-freight.com/*" || resource.arguments.url like "https://track.atlas-logistics.com/*"))};One call,two outcomes.
Switch the caller or the argument and watch the same call decide differently, with every decision landing in audit.
Site
agent shipment-tracker · acting as k.osei
browserbase/navigate(url: "https://carrier.meridian-freight.com/shipments/88412")
- Agentshipment-tracker is registered and active
- Callerk.osei verified through Okta
- Rulecarrier.meridian-freight.com is on the list
DecisionAllowed
Three agentson Browserbase.
Each one gets its own list of sites. A bundle per agent keeps one agent's list from widening another's.
shipment-tracker
Track shipments on carrier portals
Opens two carrier portals each morning and reads the status of open shipments, and is refused on any other site.
rate-sheet-reader
Read published rate sheets
Observes and extracts fuel surcharge tables from three carrier sites without ever filling a form.
release-checker
Smoke-test your own site
Clicks through checkout on staging after each deploy and reports what broke, with only your staging host on its list.
Bringing it alltogether.
Connecting Browserbase to registered agents, models, and identity in Dome completes a governed agent application.
Acting for
Control point
GatewayEvery call decided and audited
RulesGuardsQuotas
Tools
BrowserbaseAgent service
Models
Common questionsabout Browserbase.
More of whatDome works with.
Model
Claude Fable
Fable 5.1 from Anthropic and Amazon Bedrock in one failover pool, open to one group and capped by quota.
Provider
Anthropic
The Claude API behind the Model Broker: the key held in Dome, every call authorized, metered and audited.
MCP server
GitHub
The GitHub MCP server behind the Tool Gateway, with rules that decide each call on its owner and repository.
Identity
Microsoft Entra ID
Entra access tokens verified on every agent call, so rules read app roles and audit names the person.
Runtime
LangGraph
LangGraph agents with their model calls on the Model Broker and their MCP tools on the Tool Gateway.
Client
Claude Code
Claude Code on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name.
Talk with ourFDE team.
Or start free, and register your first agent in minutes. Connect it through a gateway, give it rules, and see every call it makes in one audit trail.
Talk with our FDE team
Our engineers design, build and run governed agents for the part of your business you want to change. You see what they deliver.
Agent services: web, research, payments, voice and sandboxes
Web actions, research, payments, phone calls and code execution are where agents reach past your walls. Put each service behind the Gateway, and every call is authorized, metered and audited.