AI agents call list_volumes to retrieve information from Databricks MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about volumes in a schema without creating, modifying, deleting, or executing anything. It is a straightforward data retrieval operation, consistent with the Read category. The blast radius is minimal—an AI agent misusing this tool would only expose metadata about existing volumes, not compromise data integrity or availability.
From the tool's definition Tool name 'list_volumes' and description 'List all volumes within a specific schema' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_volumes 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 list_volumes:
{
"version": "1",
"default": "deny",
"tools": {
"list_volumes": {}
}
}list_volumes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all volumes within a specific schema. It is categorised as a Read tool in the Databricks MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for list_volumes: 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.
list_volumes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_volumes 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 list_volumes. 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.
list_volumes 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.