databricks_export_run

A read tool on the Databricks MCP server.

SERVERDatabricks MCP Server SOURCEpypi:databricks-sdk-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What databricks_export_run does on Databricks MCP Server

AI agents call databricks_export_run 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.

RISK

Why databricks_export_run is rated Low

The name 'export_run' suggests retrieving/exporting the output or artifacts of a job run, which is a read operation. However, with no description available, confidence is low. Severity is medium because exporting run data could expose sensitive pipeline outputs or credentials embedded in run results.

From the tool's definition Tool name 'databricks_export_run' — description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

databricks_export_run Allowed

databricks_export_run is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "databricks_export_run": {}
  }
}

ALLOW ONLY 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_export_run call is checked against it from then on.

FAQ

Questions about databricks_export_run

What does the databricks_export_run tool do? +

databricks_export_run is a read tool on the Databricks MCP Server MCP server. It is categorised as a Read tool in the Databricks MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on databricks_export_run? +

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

databricks_export_run is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit databricks_export_run? +

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

Set action: deny in the PolicyLayer policy for databricks_export_run. 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_export_run? +

databricks_export_run 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 →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →