cancel_run · Databricks MCP Server MCP: Risk & Policy

WHAT IT DOES

What cancel_run does on Databricks MCP Server

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

Cancelling a run is an operational action that stops an active job execution. It is not purely destructive (no data is deleted), but it does trigger an external operation (stopping a running job) with real side effects. It fits Execute as the most accurate category since it modifies the state of a running process rather than reading or writing data.

From the tool's definition 'Cancel a job run' — terminates an in-progress execution

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cancel_run Rate-limited

cancel_run 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": {
    "cancel_run": {
      "limits": [
        {
          "counter": "cancel_run_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 cancel_run

What does the cancel_run tool do? +

Cancel a job run with parameter: run_id. 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 cancel_run? +

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

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

Can I rate-limit cancel_run? +

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

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

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