Connect Browserbase to Crush
Give Crush governed access to Browserbase through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Browserbase to Crush in four steps
Admins approve the server once. Everyone in Crush then gets it through the same governed connection.
- 1
Approve Browserbase in Runlayer
Add Browserbase from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Crush to Runlayer
Users add the Runlayer Plugin to Crush by following Runlayer’s setup guide. Crush reaches Browserbase’s tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Crush setup guide - 3
Sign in to Browserbase
Sign in the way Browserbase requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Browserbase from Crush
Browserbase’s approved tools appear in Crush. Every call is checked against policy and recorded.
Tools
Browserbase tools in Crush
Browserbase reports its tools when your organization connects it, so the list depends on your deployment.
Control
What Runlayer can see and stop in Crush
Some controls apply to every client at the gateway. Others depend on what Crush exposes to Runlayer.
Gateway policy (available)
Every Browserbase call from Crush passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Crush as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Crush yet, so control happens at the gateway.
Frequently asked questions
Connect more