upload_file_to_volume · Databricks MCP Server MCP

WHAT IT DOES

What upload_file_to_volume does on Databricks MCP Server

AI agents use upload_file_to_volume 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.

WHY IT NEEDS A POLICY

Why upload_file_to_volume needs a policy

Uploading files to a volume creates or stores data in Databricks storage, which is reversible (files can be deleted). This is a Write operation—it modifies the data plane but is not Destructive since uploads don't irreversibly delete or overwrite existing data. Severity is high because an AI agent could upload malicious code, large files for DoS, or exfiltrate sensitive data to accessible volumes.

From the tool's definition Tool name 'upload_file_to_volume' indicates file upload to storage. Description is empty, but the name and server context (Databricks MCP Server managing clusters, jobs, notebooks, and SQL) strongly suggest data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_file_to_volume Rate-limited

upload_file_to_volume stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "upload_file_to_volume": {
      "limits": [
        {
          "counter": "upload_file_to_volume_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Databricks MCP Server, so you can run agents against it safely.

FAQ

Questions about upload_file_to_volume

What does the upload_file_to_volume tool do? +

upload_file_to_volume. 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.

How do I enforce a policy on upload_file_to_volume? +

Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for upload_file_to_volume: 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.

What risk level is upload_file_to_volume? +

upload_file_to_volume is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit upload_file_to_volume? +

Yes. Add a rate_limit block to the upload_file_to_volume 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.

How do I block upload_file_to_volume completely? +

Set action: deny in the PolicyLayer policy for upload_file_to_volume. 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.

What MCP server provides upload_file_to_volume? +

upload_file_to_volume is provided by the Databricks MCP Server MCP server (samhavens/databricks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.