databricks_update_connection

What databricks_update_connection does on Databricks MCP Server

AI agents use databricks_update_connection 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 databricks_update_connection is rated Medium

'Update' operations reversibly modify data and configuration. Without a description, we cannot determine if this modifies connection credentials, connection metadata, or other settings, but the action is clearly not Read (which would be 'get_connection'), not Destructive (which would use 'delete'), and not Execute (which would 'run' or 'trigger'). Write is the most appropriate category.

From the tool's definition Tool name is 'databricks_update_connection' — 'update' indicates modification of existing data. Description is empty, limiting certainty. Context shows this is part of a Databricks server with 263 tools spanning SQL, Compute, Jobs, and connectivity features.

The rule that runs databricks_update_connection 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_update_connection, this is the rule to start with:

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

Questions about databricks_update_connection