mcp_run_job · Databricks MCP Server MCP: Risk & Policy

WHAT IT DOES

What mcp_run_job does on Databricks MCP Server

AI agents invoke mcp_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 mcp_run_job needs a policy

Running a job on Databricks executes arbitrary code or workflows in a distributed environment. An AI agent invoking this without proper validation could trigger unintended compute operations, data processing pipelines, or queries with side effects that depend entirely on what the job contains.

From the tool's definition Tool name 'mcp_run_job' combined with sibling tools like 'mcp_create_and_run_job_for_notebook' and 'mcp_create_and_run_serverless_dlt_pipeline' indicates this triggers execution of pre-defined Databricks jobs.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mcp_run_job Rate-limited

mcp_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": {
    "mcp_run_job": {
      "limits": [
        {
          "counter": "mcp_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 mcp_run_job

What does the mcp_run_job tool do? +

mcp_run_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 mcp_run_job? +

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

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

Can I rate-limit mcp_run_job? +

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

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

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