mcp_create_dlt_pipeline · Databricks MCP Server MCP

WHAT IT DOES

What mcp_create_dlt_pipeline does on Databricks MCP Server

AI agents use mcp_create_dlt_pipeline 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.

WHY IT NEEDS A POLICY

Why mcp_create_dlt_pipeline needs a policy

This tool creates a new Delta Live Tables pipeline, which is a reversible data modification operation. While pipelines can orchestrate data processing at scale, the creation itself is a Write operation (creates new pipeline configuration artifacts).

From the tool's definition Tool name includes 'create' and description explicitly states 'Create a Delta Live Tables pipeline', indicating creation of a new pipeline configuration in Databricks.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mcp_create_dlt_pipeline Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mcp_create_dlt_pipeline": {
      "limits": [
        {
          "counter": "mcp_create_dlt_pipeline_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Databricks MCP Server, so you can run agents against it safely.

FAQ

Questions about mcp_create_dlt_pipeline

What does the mcp_create_dlt_pipeline tool do? +

Create a Delta Live Tables pipeline. If pipeline_config includes serverless=True, serverless compute will be used. 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.

How do I enforce a policy on mcp_create_dlt_pipeline? +

Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for mcp_create_dlt_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 mcp_create_dlt_pipeline? +

mcp_create_dlt_pipeline is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mcp_create_dlt_pipeline? +

Yes. Add a rate_limit block to the mcp_create_dlt_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 mcp_create_dlt_pipeline completely? +

Set action: deny in the PolicyLayer policy for mcp_create_dlt_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 mcp_create_dlt_pipeline? +

mcp_create_dlt_pipeline is provided by the Databricks MCP Server MCP server (stephenjhsu/databricks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.