# export_notebook

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

Agent View of the PolicyLayer registry record for `export_notebook`. HTML page: https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/export-notebook

## Facts

- Tool: `export_notebook`
- Server: Databricks MCP Server (`andresgarciasobrado91/databricks-mcp-server`) — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server.md
- Homepage: https://github.com/AndresGarciaSobrado91/databricks-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "export_notebook",
    "arguments": {}
  }
}
```

## 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 own definition: "'Export a notebook from the workspace' — retrieves/downloads notebook content in various formats (SOURCE, HTML, JUPYTER, DBC)"

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Databricks MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_notebook": {}
  }
}
```

## Other tools on Databricks MCP Server (14)

- `terminate_cluster` — Destructive — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/terminate-cluster.md
- `execute_sql` — Execute — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/execute-sql.md
- `repair_run` — Execute — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/repair-run.md
- `run_job` — Execute — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/run-job.md
- `start_cluster` — Execute — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/start-cluster.md
- `get_cluster` — Read — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/get-cluster.md
- `get_job` — Read — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/get-job.md
- `get_run` — Read — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/get-run.md
- `get_run_output` — Read — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/get-run-output.md
- `list_clusters` — Read — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/list-clusters.md
- `list_files` — Read — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/list-files.md
- `list_jobs` — Read — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/list-jobs.md
- `list_notebooks` — Read — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/list-notebooks.md
- `create_cluster` — Write — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/create-cluster.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=andresgarciasobrado91-databricks-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/andresgarciasobrado91-databricks-mcp-server