run_job · Databricks MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_job does on Databricks MCP Server

AI agents invoke run_job to trigger actions in Databricks MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_job needs a policy

The 'run_job' tool executes a Databricks job, which can perform arbitrary data transformations, queries, or operations depending on the job's configuration. While the job itself is pre-defined (reducing some risk vs. direct code execution), triggering job execution is an Execute action because it causes external side effects that cannot be predicted without knowing job contents.

From the tool's definition Tool description states 'Run a Databricks job' which triggers external operations whose effects depend on job configuration and arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_job Rate-limited

run_job 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.

View as policy code

policy.json

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

RATE-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 run_job

What does the run_job tool do? +

Run a Databricks job. 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 run_job? +

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

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

Can I rate-limit run_job? +

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

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

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

// THE FULL RECORD

run_job is one line of Databricks MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →