sync_repo_and_run_notebook

THE RISK

High Risk

Why sync_repo_and_run_notebook needs a policy

This tool executes arbitrary code in a Databricks notebook environment. While the description is brief, 'run a notebook' is unambiguously an Execute action. The tool pulls potentially untrusted code and executes it, creating significant risk if an AI agent is manipulated into running notebooks with malicious or unintended logic. Notebooks can read/write data, trigger jobs, or access external systems.

From the tool's definition 'run a notebook' indicates execution of code. Combined with 'pull a repo', this tool clones/syncs remote repository content and then executes notebook code, whose effects depend on the notebook's contents and arguments.

Documented attack patterns abuse exactly the kind of access sync_repo_and_run_notebook gives an agent:

POLICY

How to control sync_repo_and_run_notebook

PolicyLayer is an MCP gateway — it sits between your AI agents and Databricks MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for sync_repo_and_run_notebook:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sync_repo_and_run_notebook": {
      "limits": [
        {
          "counter": "sync_repo_and_run_notebook_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

sync_repo_and_run_notebook stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Databricks MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Databricks MCP Server tools

Destructive dbfs_delete Delete a DBFS path Destructive delete_job Delete a Databricks job Destructive delete_workspace_object Delete a workspace notebook or directory Destructive uninstall_library Uninstall libraries from a cluster Destructive terminate_cluster Terminate a cluster Execute cancel_run Cancel a job run Execute execute_sql Execute a SQL statement Execute run_job Trigger a job run

All 38 Databricks MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Databricks MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about sync_repo_and_run_notebook

What does the sync_repo_and_run_notebook tool do? +

Pull a repo and run a notebook. It is categorised as a Execute tool in the Databricks MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sync_repo_and_run_notebook? +

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

sync_repo_and_run_notebook is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sync_repo_and_run_notebook? +

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

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

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

Enforce policy on every Databricks MCP Server tool call.

Start from Databricks MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →