Connect Metabase to Warp
Give Warp governed access to Metabase’s 45 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Metabase to Warp in four steps
Admins approve the server once. Everyone in Warp then gets it through the same governed connection.
- 1
Approve Metabase in Runlayer
Add Metabase from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Warp to Runlayer
Users add the Runlayer Plugin to Warp by following Runlayer’s setup guide. Warp reaches Metabase’s 45 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Warp setup guide - 3
Sign in to Metabase
Sign in the way Metabase requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Metabase from Warp
Metabase’s approved tools appear in Warp. Every call is checked against policy and recorded.
Tools
45 Metabase tools in Warp
Runlayer policy decides which of these Warp users can call. 25 read data only and 6 can change or delete data.
Construct query
Construct a Metabase query from a structured program with source and operations.
Create dashboard
Create a dashboard in Metabase.
Create question
Save a query as a named question in Metabase.
Execute query
Execute a previously constructed query and return the results with column metadata, row count, and execution time.
Get metric
Get details about a metric including its queryable dimensions.
Get metric field values
Get sample values and statistics for a field in a metric.
Get table
Get details about a table including its fields, related tables, and metrics.
Get table field values
Get sample values and statistics for a field in a table.
Control
What Runlayer can see and stop in Warp
Some controls apply to every client at the gateway. Others depend on what Warp exposes to Runlayer.
Gateway policy (available)
Every Metabase call from Warp passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Warp as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Warp yet, so control happens at the gateway.
Frequently asked questions
Connect more