# list_jobs

List all Databricks jobs

Agent View of the PolicyLayer registry record for `list_jobs`. HTML page: https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/list-jobs

## Facts

- Tool: `list_jobs`
- 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": "list_jobs",
    "arguments": {}
  }
}
```

## Why list_jobs is rated Low

This tool retrieves job metadata from Databricks without creating, modifying, executing, or deleting any resources. It is a non-destructive information retrieval operation. Severity is low because listing jobs exposes information about what jobs exist but does not directly compromise data or trigger any actions. The confidence is high given the explicit 'list' verb and descriptive purpose.

From the tool's own definition: "Tool name 'list_jobs' and description 'List all Databricks jobs' indicate a query/retrieval operation with no modification or execution of resources."

## Use case

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

## 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` — Read — https://policylayer.com/tools/andresgarciasobrado91-databricks-mcp-server/get-run.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_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