import_notebook · Databricks MCP Server MCP: Risk & Policy

WHAT IT DOES

What import_notebook does on Databricks MCP Server

AI agents use import_notebook 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 import_notebook needs a policy

Importing a notebook creates new data/code artifacts in the workspace. While reversible (notebooks can be deleted), this is a Write operation as it modifies the workspace state by introducing executable code. Severity is high because imported notebooks can contain arbitrary code that may be executed by other users or jobs, potentially affecting data access and system security.

From the tool's definition Tool description states 'Import a notebook' with parameters for 'path' and 'content', which creates or adds a notebook resource to the Databricks workspace.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_notebook Rate-limited

import_notebook 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": {
    "import_notebook": {
      "limits": [
        {
          "counter": "import_notebook_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 import_notebook

What does the import_notebook tool do? +

Import a notebook; parameters: path, content (base64 or text), format (optional). 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 import_notebook? +

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

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

Can I rate-limit import_notebook? +

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

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

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