export_notebook

Export a notebook from the workspace with parameters: path (string, required), format (string, optional, one of: SOURCE, HTML, JUPYTER, DBC)

SERVERDatabricks MCP Server SOURCEandresgarciasobrado91/databricks-mcp-server

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/andresgarciasobrado91-databricks-mcp-server/export-notebook.md

WHAT IT DOES

What export_notebook does on Databricks MCP Server

AI agents call export_notebook 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 export_notebook is rated Low

Exporting a notebook is a read operation: it retrieves the notebook content from the Databricks workspace without modifying or deleting anything. Severity is medium because notebooks may contain sensitive code, credentials, or proprietary logic that could be exposed if an AI agent exports them without authorization.

From the tool's definition 'Export a notebook from the workspace' — retrieves/downloads notebook content in various formats (SOURCE, HTML, JUPYTER, DBC)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

export_notebook Allowed

export_notebook 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": {
    "export_notebook": {}
  }
}

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

FAQ

Questions about export_notebook

What does the export_notebook tool do? +

Export a notebook from the workspace with parameters: path (string, required), format (string, optional, one of: SOURCE, HTML, JUPYTER, DBC). 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 export_notebook? +

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

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

Can I rate-limit export_notebook? +

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

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

export_notebook is provided by the Databricks MCP Server MCP server (andresgarciasobrado91/databricks-mcp-server). 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 15 Databricks MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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