# databricks_metastore_summary

A read tool on the Databricks MCP Server MCP server.

Agent View of the PolicyLayer registry record for `databricks_metastore_summary`. HTML page: https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-metastore-summary

## Facts

- Tool: `databricks_metastore_summary`
- Server: Databricks MCP Server (`pypi:databricks-sdk-mcp`) — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp.md
- Install: `npx -y pypi:databricks-sdk-mcp`
- Homepage: https://github.com/pramodbhatofficial/databricks-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "databricks_metastore_summary",
    "arguments": {}
  }
}
```

## Why databricks_metastore_summary is rated Low

Metastore summary operations typically fetch and report statistics or overview data about catalog objects and configurations. Despite the empty description reducing confidence slightly, the naming convention and context of a metadata management system (Databricks Unity Catalog) indicate this is a query/retrieval function with no side effects.

From the tool's own definition: "Tool name 'metastore_summary' indicates retrieval of summary information about a metastore. The suffix 'summary' strongly suggests a read-only query operation that retrieves aggregated metadata without modification."

## Use case

AI agents call databricks_metastore_summary 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Databricks MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "databricks_metastore_summary": {}
  }
}
```

## Other tools on Databricks MCP Server (261)

- `databricks_dbfs_delete` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-dbfs-delete.md
- `databricks_delete_app` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-app.md
- `databricks_delete_catalog` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-catalog.md
- `databricks_delete_connection` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-connection.md
- `databricks_delete_database_instance` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-database-instance.md
- `databricks_delete_experiment` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-experiment.md
- `databricks_delete_external_location` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-external-location.md
- `databricks_delete_function` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-function.md
- `databricks_delete_git_credential` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-git-credential.md
- `databricks_delete_global_init_script` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-global-init-script.md
- `databricks_delete_group` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-group.md
- `databricks_delete_instance_pool` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-instance-pool.md
- `databricks_delete_job` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-job.md
- `databricks_delete_metastore` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-metastore.md
- `databricks_delete_online_table` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-online-table.md
- `databricks_delete_pipeline` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-pipeline.md
- `databricks_delete_quality_monitor` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-quality-monitor.md
- `databricks_delete_recipient` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-recipient.md
- `databricks_delete_registered_model` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-registered-model.md
- `databricks_delete_run` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-run.md
- `databricks_delete_schema` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-schema.md
- `databricks_delete_secret` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-secret.md
- `databricks_delete_secret_scope` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-secret-scope.md
- `databricks_delete_service_principal` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-service-principal.md
- `databricks_delete_serving_endpoint` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-serving-endpoint.md
- `databricks_delete_share` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-share.md
- `databricks_delete_storage_credential` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-storage-credential.md
- `databricks_delete_table` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-table.md
- `databricks_delete_token` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-token.md
- `databricks_delete_token_management` — Destructive — https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-delete-token-management.md
- …and 231 more: https://policylayer.com/tools/io-github-pramodbhatofficial-databricks-sdk-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=io-github-pramodbhatofficial-databricks-sdk-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-pramodbhatofficial-databricks-sdk-mcp