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