Delete a file or directory in DBFS with parameters: dbfs_path, recursive (optional)
AI agents call dbfs_delete to permanently remove resources in Databricks MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes files or directories from Databricks File System (DBFS) without undo capability. It is Destructive rather than Execute because the action is deletion, which cannot be reversed. The 'recursive' parameter amplifies risk by allowing bulk deletion. Severity is high because data loss in a shared analytics platform can impact multiple users and workflows, though it is not Financial.
From the tool's definition Tool name is 'dbfs_delete' and description states 'Delete a file or directory in DBFS'. The 'delete' operation with 'recursive' parameter indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a file or directory in DBFS with parameters: dbfs_path, recursive (optional). It is categorised as a Destructive tool in the Databricks MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for dbfs_delete: 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.
dbfs_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the dbfs_delete 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 dbfs_delete. 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.
dbfs_delete is provided by the Databricks MCP Server MCP server (robkisk/databricks-mcp). 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 →