list_jobs

THE RISK

Low Risk

Why list_jobs needs a policy

This tool retrieves or queries job metadata from Databricks without creating, modifying, executing, or deleting anything. It is a passive read operation with no side effects, making it a straightforward Read category tool with low severity.

From the tool's definition Tool name is 'list_jobs' and description states 'List Databricks jobs' — a query/retrieval operation with no modification or deletion of data.

Documented attack patterns abuse exactly the kind of access list_jobs gives an agent:

POLICY

How to control list_jobs

PolicyLayer is an MCP gateway — it sits between your AI agents and Databricks MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_jobs:

policy.json

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

list_jobs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Databricks MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Databricks MCP Server tools

Destructive dbfs_delete Delete a DBFS path Destructive delete_job Delete a Databricks job Destructive delete_workspace_object Delete a workspace notebook or directory Destructive uninstall_library Uninstall libraries from a cluster Destructive terminate_cluster Terminate a cluster Execute cancel_run Cancel a job run Execute execute_sql Execute a SQL statement Execute run_job Trigger a job run

All 38 Databricks MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_jobs

What does the list_jobs tool do? +

List Databricks jobs. It is categorised as a Read tool in the Databricks MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_jobs? +

Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for list_jobs: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Databricks MCP Server. Nothing to install.

What risk level is list_jobs? +

list_jobs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_jobs? +

Yes. Add a rate_limit block to the list_jobs rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block list_jobs completely? +

Set action: deny in the PolicyLayer policy for list_jobs. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides list_jobs? +

list_jobs is provided by the Databricks MCP Server MCP server (markov-kernel/databricks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Databricks MCP Server tool call.

Start from Databricks MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →