databricks_list_pipelines
List DLT pipelines in the workspace.
This record as markdown: /tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-list-pipelines.md
What databricks_list_pipelines does on Databricks MCP Server
AI agents call databricks_list_pipelines to retrieve information from Databricks MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why databricks_list_pipelines is rated Low
This tool queries and returns information about existing DLT (Delta Live Tables) pipelines without creating, modifying, deleting, or executing anything. It is a pure read operation with minimal blast radius—only exposing metadata about pipelines in the workspace.
From the tool's definition Tool name 'list_pipelines' and description 'List DLT pipelines in the workspace' indicate a data retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs databricks_list_pipelines safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Databricks MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For databricks_list_pipelines, this is the rule to start with:
databricks_list_pipelines is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Databricks MCP Server, apply this rule, and every databricks_list_pipelines call is checked against it from then on.
Questions about databricks_list_pipelines
List DLT pipelines in the 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 databricks_list_pipelines: 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.
databricks_list_pipelines 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 databricks_list_pipelines 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 databricks_list_pipelines. 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.
databricks_list_pipelines is provided by the Databricks MCP Server MCP server (pypi:databricks-sdk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Databricks MCP Server, and thousands of servers like it.
This server
Across the catalogue