AI agents use move_dbfs_path 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.
Moving or renaming files is a write operation that modifies filesystem metadata and potentially directory structures. It is reversible (unlike deletion), so it does not qualify as Destructive. The severity is medium because misuse could disrupt data workflows or organizational structure in DBFS, but the impact is scoped to filesystem organization rather than data loss or code execution.
From the tool's definition Tool description states 'Move/rename a file or directory in DBFS' — this modifies the location/metadata of files reversibly. The action is a standard filesystem operation that changes state but can be undone (moved again or renamed back).
Documented attack patterns abuse exactly the kind of access move_dbfs_path gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Databricks MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for move_dbfs_path:
{
"version": "1",
"default": "deny",
"tools": {
"move_dbfs_path": {
"limits": [
{
"counter": "move_dbfs_path_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_dbfs_path 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.
Free to start. No card required.
Move/rename a file or directory in DBFS. 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 move_dbfs_path: 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.
move_dbfs_path 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 move_dbfs_path 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 move_dbfs_path. 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.
move_dbfs_path is provided by the Databricks MCP Server MCP server (pulkitxchadha/awesome-databricks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Databricks MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
86 Databricks MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.