# get_run

Get information about a specific job run with parameters: run_id (string, required), include_history (boolean, optional)

Agent View of the PolicyLayer registry record for `get_run`. HTML page: https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/get-run

## Facts

- Tool: `get_run`
- Server: Databricks MCP Server (`andresgarciasobrado91/databricks-mcp-server`) — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server.md
- Homepage: https://github.com/AndresGarciaSobrado91/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": "get_run",
    "arguments": {}
  }
}
```

## Why get_run is rated Low

This tool retrieves metadata and history about a completed or in-progress job run. It performs a read-only query operation without creating, modifying, deleting, executing code, or moving money. The blast radius of misuse is minimal—an agent could retrieve sensitive job information but cannot alter system state or resources.

From the tool's own definition: "Tool name 'get_run' and description 'Get information about a specific job run' indicate data retrieval with no modification or side effects. The parameters (run_id and optional include_history) are for querying/filtering only."

## Use case

AI agents call get_run 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": {
    "get_run": {}
  }
}
```

## Other tools on Databricks MCP Server (14)

- `terminate_cluster` — Destructive — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/terminate-cluster.md
- `execute_sql` — Execute — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/execute-sql.md
- `repair_run` — Execute — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/repair-run.md
- `run_job` — Execute — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/run-job.md
- `start_cluster` — Execute — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/start-cluster.md
- `export_notebook` — Read — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/export-notebook.md
- `get_cluster` — Read — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/get-cluster.md
- `get_job` — Read — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/get-job.md
- `get_run_output` — Read — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/get-run-output.md
- `list_clusters` — Read — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/list-clusters.md
- `list_files` — Read — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/list-files.md
- `list_jobs` — Read — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/list-jobs.md
- `list_notebooks` — Read — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/list-notebooks.md
- `create_cluster` — Write — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/create-cluster.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=andresgarciasobrado91-databricks-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/andresgarciasobrado91-databricks-mcp-server