Delete a Databricks job with parameter: job_id
AI agents call delete_job 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.
This tool permanently removes a Databricks job, which is an irreversible destructive action. Job deletion cannot be undone and represents permanent loss of job configuration, history, and associated resources. While not a direct financial impact, the high confidence that this causes unrecoverable data/configuration loss places it in the Destructive category with high severity due to operational impact.
From the tool's definition Tool name 'delete_job' and description explicitly state deletion of a Databricks job. Deletion is irreversible and cannot be undone.
Attacks that exploit this kind of access
Delete a Databricks job with parameter: job_id. 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 delete_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.
delete_job 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 delete_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.
Set action: deny in the PolicyLayer policy for delete_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.
delete_job 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.
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 →