list_jobs

List the most recent render jobs + how many are currently running, so you can report on or resume in-flight work.

SERVERHermoso SOURCEhttps://app.hermoso.ai/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/hermoso/list-jobs.md

WHAT IT DOES

What list_jobs does on Hermoso

AI agents call list_jobs to retrieve information from Hermoso without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_jobs is rated Low

This tool retrieves and reports on the status of existing render jobs without creating, modifying, deleting, or executing any operations. It is purely informational, allowing users to check job history and current queue status. The blast radius of misuse is minimal—an attacker could only gain visibility into job metadata, not affect job execution, billing, or data integrity.

From the tool's definition Tool name 'list_jobs' and description 'List the most recent render jobs + how many are currently running' indicate retrieval and querying of job status data with no modification or execution of jobs themselves.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_jobs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hermoso, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_jobs, this is the rule to start with:

list_jobs Allowed

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

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hermoso, apply this rule, and every list_jobs call is checked against it from then on.

FAQ

Questions about list_jobs

What does the list_jobs tool do? +

List the most recent render jobs + how many are currently running, so you can report on or resume in-flight work. It is categorised as a Read tool in the Hermoso MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_jobs? +

Register the Hermoso 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 Hermoso. 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 Hermoso MCP server (https://app.hermoso.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hermoso, and thousands of servers like it.

This server

All 896 Hermoso tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →