Upload a small file to DBFS with parameters: dbfs_path, content_base64
AI agents use dbfs_put to create or update resources in Databricks MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Databricks MCP Server environment.
The tool creates or modifies files in DBFS by uploading content. This is a Write operation rather than Read (retrieves data), Execute (runs code/commands), or Destructive (irreversible deletion). It is reversible since files can be modified or deleted afterward.
From the tool's definition Tool name is 'dbfs_put' and description states 'Upload a small file to DBFS', which is a file creation/modification operation. DBFS (Databricks File System) is a distributed storage layer; uploading files is a reversible write operation.
Attacks that exploit this kind of access
Upload a small file to DBFS with parameters: dbfs_path, content_base64. It is categorised as a Write tool in the Databricks MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for dbfs_put: 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_put is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dbfs_put 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_put. 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_put 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 →