List files and directories in DBFS (Databricks File System).
AI agents call list_dbfs_files to retrieve information from Databricks MCP Server Template without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves directory and file metadata from the Databricks File System without modifying, deleting, or executing anything. It is a pure read operation with minimal blast radius—an AI agent listing files cannot cause irreversible damage, though it could potentially discover sensitive file paths or metadata if access controls are misconfigured.
From the tool's definition Tool name contains 'list' and description states 'List files and directories in DBFS'. No mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
List files and directories in DBFS (Databricks File System). It is categorised as a Read tool in the Databricks MCP Server Template MCP Server, which means it retrieves data without modifying state.
Register the Databricks MCP Server Template MCP server in PolicyLayer and add a rule for list_dbfs_files: 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 Template. Nothing to install.
list_dbfs_files 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 list_dbfs_files 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 list_dbfs_files. 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.
list_dbfs_files is provided by the Databricks MCP Server Template MCP server (max-nienu/mnienu-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →