List all SQL warehouses in the Databricks workspace.
AI agents call list_warehouses 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 retrieves information about SQL warehouses in the Databricks workspace. It performs a query/list operation with no side effects, no data modification, no code execution, and no deletion. It falls clearly under the Read category. Severity is low because listing warehouses exposes organizational infrastructure information but does not enable direct access to data or operations.
From the tool's definition Tool name 'list_warehouses' and description 'List all SQL warehouses' indicate a read-only operation that retrieves warehouse metadata without modifying or executing operations.
Attacks that exploit this kind of access
List all SQL warehouses in the Databricks workspace. 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_warehouses: 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_warehouses 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_warehouses 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_warehouses. 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_warehouses is provided by the Databricks MCP Server MCP server (moma1992/mcp-databricks-app). 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 →