uninstall_library · Databricks MCP Server MCP: Risk & Policy

WHAT IT DOES

What uninstall_library does on Databricks MCP Server

AI agents use uninstall_library to create or update resources in Databricks MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Databricks MCP Server environment.

WHY IT NEEDS A POLICY

Why uninstall_library needs a policy

Uninstalling a library modifies the cluster's configuration by removing a library, but this is generally reversible (the library can be reinstalled). It does not delete data or execute arbitrary code, making Write the most appropriate category. Severity is medium because misuse could break running jobs or workflows dependent on the library.

From the tool's definition 'Uninstall a library from a cluster' - removes a library installation from a cluster

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

uninstall_library Rate-limited

uninstall_library stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "uninstall_library": {
      "limits": [
        {
          "counter": "uninstall_library_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 uninstall_library

What does the uninstall_library tool do? +

Uninstall a library from a cluster with parameters: cluster_id, libraries. It is categorised as a Write tool in the Databricks MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

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 Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

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 (robkisk/databricks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.