Databricks curbs AI agent dangers

Databricks Unity Catalog introduces granular control and logging for AI agents, preventing unauthorized actions and providing a complete audit trail.

Daniel Singer

Editor, StartupHub.ai

May 19 at 7:02 PMUpdated Aug 22, 20263 min read

Databricks enhances AI agent security with Unity Catalog.

Visual TL;DR

AI agent dangersDriver

From the article 9+ mentionsThe era of autonomous AI agents making critical decisions in production is here, bringing with it significant risks.

Unrestricted tool accessDriver

agents had access to all available functions without fine-grained control

From the articleThe core issue: a lack of control over which tools agents can access and no record of their actions.

Invisible agent actionsDriver

tool calls were absent from standard logs, leaving no audit trail

From the article 2 mentionsDatabricks is addressing this gap with new capabilities in its Unity Catalog, aimed at securing agent actions.

Databricks Unity CatalogCore

extends governance to all connected tools, mirroring data management

From the article 4 mentionsDatabricks is introducing granular control and comprehensive logging for AI agents through Unity Catalog MCP governance.

Granular controlEffect

restricting write access or limiting administrative functions to specific users

From the article 3 mentionsDatabricks is introducing granular control and comprehensive logging for AI agents through Unity Catalog MCP governance.

Complete audit trailEffect

providing a complete record of all agent actions and tool calls

From the article 2 mentionsCrucially, when things went wrong, there was no audit trail.

Curbs AI agent dangersOutcome

preventing unauthorized actions and providing a complete audit trail

Contents(3)

The era of autonomous AI agents making critical decisions in production is here, bringing with it significant risks. Incidents of agents destructively wiping databases or deleting vast amounts of data are no longer theoretical, even when agents operate within their granted permissions. The core issue: a lack of control over which tools agents can access and no record of their actions.

Databricks is addressing this gap with new capabilities in its Unity Catalog, aimed at securing agent actions. The platform now extends governance to all connected tools, mirroring how data itself is managed.

The problem: Unrestricted access, invisible actions

Traditionally, if an AI agent was authorized to connect to a toolset, it had access to all available functions. This meant no fine-grained control, like restricting write access or limiting administrative functions to specific users. Crucially, when things went wrong, there was no audit trail.

Tool calls were absent from standard logs, leaving no record of what an agent did, with what parameters, or on whose behalf. This blindness makes it impossible to prevent unintended consequences or investigate incidents after they occur.

The solution: Unity Catalog MCP governance

Databricks is introducing granular control and comprehensive logging for AI agents through Unity Catalog MCP governance. This allows administrators to define precise rules for how agents interact with external tools, known as Managed Cloud Platform (MCP) tools.

Service policies, written in SQL, enable administrators to specify exactly which tools an agent can call and under what conditions. These policies can evaluate arguments and context, blocking or requiring consent for specific actions.

This is a significant step towards agentic AI security, preventing unauthorized agent behavior.

How it works

Administrators define service policies as SQL functions within Unity Catalog. These functions take the caller (actor) and the requested action (context) as input, returning an allow or deny decision with a reason.

For example, a policy could block all file deletion requests or permit merging pull requests only for approved engineers.

Once defined, these policies are attached to MCP services via the Databricks AI Gateway service policies. The gateway enforces these rules in real time for every tool call.

Simultaneously, all tool interactions are captured as entries in a Delta table within Unity Catalog. This includes the tool name, arguments, result, user identity, and whether the call was allowed or denied, providing a complete, queryable audit log.

This capability is currently available in gated beta, extending existing data governance principles to the realm of AI agents.

© 2026 StartupHub.ai. All rights reserved. You may not republish this article in full without a license. Search engines and AI research tools may crawl and summarize for reference. Bulk reproduction or model training requires a license. See our terms.

#Databricks #Unity Catalog #AI Security #Agentic AI #LLM Ops #Data Governance #Cloud Computing

Written by

Daniel Singer

Editor, StartupHub.ai

Daniel Singer is the editor of StartupHub.ai, a technology expert and thought leader on AI and its applications across sectors, from fintech and healthcare to developer tooling and consumer software. He writes and tests the tools covered here thoroughly and regularly, and built StartupHub.ai to give founders, operators and buyers a clearer read on what they are actually being sold.