databricks_get_database_instance

What databricks_get_database_instance does on Databricks MCP Server

AI agents call databricks_get_database_instance to retrieve information from Databricks MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why databricks_get_database_instance is rated Low

The 'get' verb strongly suggests a read-only operation that retrieves database instance information. No indication of modification, deletion, code execution, or financial operations. Empty description lowers confidence slightly, but the semantic meaning of the name is clear enough to classify as Read with medium-high confidence.

From the tool's definition Tool name 'databricks_get_database_instance' uses the verb 'get', which typically retrieves or queries data without side effects. The description is empty, limiting direct confirmation, but the naming pattern is consistent with retrieval operations.

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "databricks_get_database_instance": {}
  }
}

Questions about databricks_get_database_instance