databricks_delete_recipient
A destructive tool on the Databricks MCP server.
This record as markdown: /tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-recipient.md
What databricks_delete_recipient does on Databricks MCP Server
AI agents call databricks_delete_recipient 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.
Why databricks_delete_recipient is rated Critical
The tool name directly indicates a delete operation on a recipient entity. In Databricks, recipients are key infrastructure elements for data sharing. Deleting a recipient is an irreversible action that would break data sharing relationships and cannot be recovered. This matches the Destructive category definition (irreversibly deletes data).
From the tool's definition Tool name 'databricks_delete_recipient' contains the verb 'delete', which indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs databricks_delete_recipient safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Databricks MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For databricks_delete_recipient, this is the rule to start with:
databricks_delete_recipient is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Databricks MCP Server, apply this rule, and every databricks_delete_recipient call is checked against it from then on.
Questions about databricks_delete_recipient
databricks_delete_recipient is a destructive tool on the Databricks MCP Server MCP server. 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 databricks_delete_recipient: 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.
databricks_delete_recipient 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 databricks_delete_recipient 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 databricks_delete_recipient. 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.
databricks_delete_recipient is provided by the Databricks MCP Server MCP server (pypi:databricks-sdk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Databricks MCP Server, and thousands of servers like it.
Across the catalogue