What problem does it solve? Databricks administrators and data engineers struggle to answer governance questions like who accessed a table, what feeds a downstream dataset, or how much DBU a workspace consumed, because this data lives scattered across Unity Catalog system tables and volume storage. ## Core Features & Use Cases - System Table Queries: Ready-to-use SQL for audit logs, table and column lineage, billing/DBU usage, compute events, job run history, and query performance across the system catalog schemas. - Volume File Operations: Upload, download, list, and organize files in Unity Catalog Volumes using MCP tools, the Python SDK, or SQL read_files. - Governance & Access Control: Grant patterns for system schemas and volumes, plus audit queries for permission changes and sensitive data access. - Use Case: A platform engineer notices a spike in costs and uses the billing queries to break down DBU consumption by workspace and SKU, then checks audit logs to see which clusters drove the increase. ## Quick Start Ask the assistant to show which tables feed into a specific Unity Catalog table using system.access.table_lineage, or to upload a local CSV file into a volume path.