How does Ferentin secure Databricks access?

Requests through the Databricks integration are covered by unity catalog governance, service principal auth and workspace scoped endpoint. These controls are applied by Ferentin, not by Databricks, so they hold across every connected agent.

How do I connect Databricks to Ferentin?

Open the Ferentin admin console, add Databricks as a new connection and authenticate with API key. You then choose which permissions and which tools your agents may use, and the connection goes live for everyone covered by your policies.

Is the Databricks integration generally available?

The Databricks integration is currently beta on Ferentin.

MCP Servers

Databricks

Beta

Query the Databricks lakehouse — SQL warehouses, Unity Catalog functions, Genie spaces, and vector search.

MCP ServersDatabricksLakehouseAnalytics

Configure Setup guide

How it works

Every agent request passes through Ferentin policy before it reaches Databricks.

AI agentAsks for something
Ferentin policies
- Unity catalog governance
- Service principal auth
- Workspace scoped endpoint
Databricks MCP serverAuthorized connection
Governed resultMasked, logged, returned

What you can do with Databricks

SQL warehouse query
Unity catalog functions
Genie spaces
Vector search

Overview

Databricks is a unified data and AI platform built on the lakehouse architecture, combining data warehousing, ETL, and machine learning on open formats with Unity Catalog providing centralized governance across data and AI assets.

Website Developer docs

Ferentin integration

Ferentin connects to a Databricks managed MCP server on your own workspace host using a personal access token or service-principal OAuth token. Because every endpoint is workspace-scoped, the server URL is supplied at install time. Unity Catalog grants remain the authorization boundary for every tool call.

Connection details

Status: Beta
Integration type: Remote MCP server
Authentication: API key
Hosting: Vendor-hosted endpoint

Configure Setup guide

Security controls3

Unity catalog governance
Service principal auth
Workspace scoped endpoint

Technical details

Vendor: Databricks

The URL shipped with this card is an EXAMPLE host and will not resolve — installing without overriding the endpoint fails to connect.
Managed MCP servers are in Public Preview; endpoint paths and available servers may change.
Unity Catalog is the authorization boundary. Ferentin sends one token per instance, so every caller on that instance acts as that single principal — use a least-privilege service principal rather than a workspace admin's PAT.
Azure Databricks workspaces use an *.azuredatabricks.net host; GCP workspaces use *.gcp.databricks.com.
Databricks does not support Dynamic Client Registration on these endpoints, so Ferentin uses token auth rather than an OAuth authorization-code flow.

Frequently asked about Databricks

What can AI agents do with Databricks through Ferentin?: Through Ferentin, agents can use Databricks for SQL warehouse query, unity catalog functions, genie spaces and vector search. Every call is checked against your Ferentin policies first.
How does Ferentin secure Databricks access?: Requests through the Databricks integration are covered by unity catalog governance, service principal auth and workspace scoped endpoint. These controls are applied by Ferentin, not by Databricks, so they hold across every connected agent.
How do I connect Databricks to Ferentin?: Open the Ferentin admin console, add Databricks as a new connection and authenticate with API key. You then choose which permissions and which tools your agents may use, and the connection goes live for everyone covered by your policies.
Is the Databricks integration generally available?: The Databricks integration is currently beta on Ferentin.