databricks_metastore_summary
A read tool on the Databricks MCP server.
This record as markdown: /tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-metastore-summary.md
What databricks_metastore_summary does on Databricks MCP Server
AI agents call databricks_metastore_summary to retrieve information from Databricks MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why databricks_metastore_summary is rated Low
Metastore summary operations typically fetch and report statistics or overview data about catalog objects and configurations. Despite the empty description reducing confidence slightly, the naming convention and context of a metadata management system (Databricks Unity Catalog) indicate this is a query/retrieval function with no side effects.
From the tool's definition Tool name 'metastore_summary' indicates retrieval of summary information about a metastore. The suffix 'summary' strongly suggests a read-only query operation that retrieves aggregated metadata without modification.
Attacks that exploit this kind of access
The rule that runs databricks_metastore_summary safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Databricks MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For databricks_metastore_summary, this is the rule to start with:
databricks_metastore_summary is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Databricks MCP Server, apply this rule, and every databricks_metastore_summary call is checked against it from then on.
Questions about databricks_metastore_summary
databricks_metastore_summary is a read tool on the Databricks MCP Server MCP server. It is categorised as a Read tool in the Databricks MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for databricks_metastore_summary: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Databricks MCP Server. Nothing to install.
databricks_metastore_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the databricks_metastore_summary rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for databricks_metastore_summary. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
databricks_metastore_summary is provided by the Databricks MCP Server MCP server (pypi:databricks-sdk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Databricks MCP Server, and thousands of servers like it.
This server
Across the catalogue