list_jobs

THE RISK

Low Risk

Why list_jobs needs a policy

This tool queries and returns information about jobs without modifying, deleting, or executing any operations. It is a straightforward data retrieval function, making it a Read category tool with low severity risk.

From the tool's definition Tool name 'list_jobs' and description 'List all jobs in a specific repository' indicate a retrieval operation with no side effects.

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 Mcp Dagster, 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 Mcp Dagster — 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 Mcp Dagster tools

Destructive terminate_run Terminate an in-progress Dagster run Execute launch_run Launch a Dagster job run Execute materialize_asset Materialize a specific Dagster asset Read get_asset_info Get detailed information about a specific asset Read get_run_info Get detailed information about a specific run Read list_assets List all assets in a specific repository Read list_repositories List all available Dagster repositories Read recent_runs Get recent Dagster runs

All 9 Mcp Dagster 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 all jobs in a specific repository. It is categorised as a Read tool in the Mcp Dagster MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_jobs? +

Register the Mcp Dagster 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 Mcp Dagster. 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 Mcp Dagster MCP server (kyryl-opens-ml/mcp-server-dagster). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Dagster tool call.

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

CHECK YOUR STACK →