install_library · Databricks MCP Server MCP: Risk & Policy

WHAT IT DOES

What install_library does on Databricks MCP Server

AI agents invoke install_library to trigger actions in Databricks MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why install_library needs a policy

Installing libraries on a cluster is an Execute-category action: it triggers an external operation (library installation) on a running cluster, modifying its runtime environment. While it has a Write-like aspect, the primary risk is execution of arbitrary packages on shared infrastructure, which could introduce malicious code, destabilize the cluster, or create security vulnerabilities.

From the tool's definition 'Install a library on a cluster' - installs software packages onto a running Databricks cluster, triggering an external operation that modifies the cluster's runtime environment

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

install_library Rate-limited

install_library stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "install_library": {
      "limits": [
        {
          "counter": "install_library_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 install_library

What does the install_library tool do? +

Install a library on a cluster with parameters: cluster_id, libraries. It is categorised as a Execute tool in the Databricks MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on install_library? +

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

install_library is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit install_library? +

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

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

install_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.