Terminate a Databricks cluster
AI agents call terminate_cluster to permanently remove resources in Databricks MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Terminating a cluster is an irreversible disruptive action that stops all running workloads on the cluster, interrupts any jobs or notebooks executing on it, and cannot be undone (the cluster must be restarted from scratch). This matches the Destructive category. Severity is high because misuse by an AI agent could kill production workloads and cause data loss or significant downtime across all users of that cluster.
From the tool's definition terminate_cluster — 'Terminate a Databricks cluster'
Attacks that exploit this kind of access
Terminate a Databricks cluster. It is categorised as a Destructive tool in the Databricks MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for terminate_cluster: 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.
terminate_cluster is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the terminate_cluster 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.
Set action: deny in the PolicyLayer policy for terminate_cluster. 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.
terminate_cluster 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →