AI agents use create_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.
The 'create' operation is reversible (volumes can be deleted), so this falls under Write rather than Destructive. However, creating volumes is a workspace-modifying action with potentially significant blast radius if an agent creates many volumes or resources named maliciously, impacting storage quotas and workspace organization.
From the tool's definition Tool name 'create_volume' indicates a data structure creation operation. Databricks volumes are storage containers for data. The tool creates (not merely reads) persistent data storage resources within the Databricks workspace.
Documented attack patterns abuse exactly the kind of access create_volume 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 create_volume:
{
"version": "1",
"default": "deny",
"tools": {
"create_volume": {
"limits": [
{
"counter": "create_volume_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_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.
Free to start. No card required.
create_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.
Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_volume 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 create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_volume 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.