databricks_start_pipeline

A execute tool on the Databricks MCP server.

SERVERDatabricks MCP Server SOURCEpypi:databricks-sdk-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-start-pipeline.md

WHAT IT DOES

What databricks_start_pipeline does on Databricks MCP Server

AI agents invoke databricks_start_pipeline to trigger actions in Databricks MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why databricks_start_pipeline is rated High

Starting a pipeline triggers automated workflows and data processing jobs whose side effects (data transformations, writes to tables/catalogs, resource consumption) cannot be fully predicted without knowing pipeline configuration. This is Execute rather than Write because it initiates external orchestrated operations.

From the tool's definition Tool name 'databricks_start_pipeline' indicates triggering execution of a data pipeline, which starts external operations whose effects depend on pipeline configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs databricks_start_pipeline 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_start_pipeline, this is the rule to start with:

databricks_start_pipeline Rate-limited

databricks_start_pipeline stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "databricks_start_pipeline": {
      "limits": [
        {
          "counter": "databricks_start_pipeline_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Databricks MCP Server, apply this rule, and every databricks_start_pipeline call is checked against it from then on.

FAQ

Questions about databricks_start_pipeline

What does the databricks_start_pipeline tool do? +

databricks_start_pipeline is a execute tool on the Databricks MCP Server MCP server. It is categorised as a Execute tool in the Databricks MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on databricks_start_pipeline? +

Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for databricks_start_pipeline: 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.

What risk level is databricks_start_pipeline? +

databricks_start_pipeline is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit databricks_start_pipeline? +

Yes. Add a rate_limit block to the databricks_start_pipeline 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.

How do I block databricks_start_pipeline completely? +

Set action: deny in the PolicyLayer policy for databricks_start_pipeline. 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.

What MCP server provides databricks_start_pipeline? +

databricks_start_pipeline 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.

KEEP EXPLORING

More on Databricks MCP Server, and thousands of servers like it.

This server

All 262 Databricks MCP Server tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP →start_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →