uninstall_library

THE RISK

Critical Risk

Why uninstall_library needs a policy

Uninstalling libraries from a cluster is an irreversible removal action that could break running jobs, notebooks, or workflows depending on those libraries. The removal of dependencies cannot be automatically undone and may cause cascading failures across workloads on the affected cluster.

From the tool's definition Uninstall libraries from a cluster

Documented attack patterns abuse exactly the kind of access uninstall_library gives an agent:

POLICY

How to control uninstall_library

PolicyLayer is an MCP gateway — it sits between your AI agents and Databricks MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for uninstall_library:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "uninstall_library"
  ]
}

uninstall_library disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Databricks MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Databricks MCP Server tools

Destructive dbfs_delete Delete a DBFS path Destructive delete_job Delete a Databricks job Destructive delete_workspace_object Delete a workspace notebook or directory Destructive terminate_cluster Terminate a cluster Execute cancel_run Cancel a job run Execute execute_sql Execute a SQL statement Execute run_job Trigger a job run Execute run_notebook Submit a one-time notebook run

All 38 Databricks MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Databricks MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about uninstall_library

What does the uninstall_library tool do? +

Uninstall libraries from a 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.

How do I enforce a policy on uninstall_library? +

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

uninstall_library is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit uninstall_library? +

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

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

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

Enforce policy on every Databricks MCP Server tool call.

Start from Databricks MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →