databricks_files_get_metadata
A read tool on the Databricks MCP server.
This record as markdown: /tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-files-get-metadata.md
What databricks_files_get_metadata does on Databricks MCP Server
AI agents call databricks_files_get_metadata 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_files_get_metadata is rated Low
The tool name clearly suggests a metadata retrieval operation ('get_metadata'), which is a read operation that queries data without side effects. No description was provided, which slightly reduces confidence, but the semantic meaning of the tool name strongly indicates it retrieves file metadata from Databricks rather than modifying, executing, or deleting data.
From the tool's definition Tool name 'databricks_files_get_metadata' indicates retrieval of file metadata; 'get' and 'metadata' are characteristic of read-only operations that retrieve information without modification.
Attacks that exploit this kind of access
The rule that runs databricks_files_get_metadata 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_files_get_metadata, this is the rule to start with:
databricks_files_get_metadata 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_files_get_metadata call is checked against it from then on.
Questions about databricks_files_get_metadata
databricks_files_get_metadata 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_files_get_metadata: 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_files_get_metadata 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_files_get_metadata 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_files_get_metadata. 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_files_get_metadata 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