AI agents call list_generation_jobs to retrieve information from Raven without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Max jobs to return. Default 25. |
status | string | — | Filter by status: draft, needs_runner, submitted, completed, failed. |
media_type | string | — | Filter by media type. |
Parameters from the server's own tool schema.
This tool performs a read-only query of existing generation job metadata. It returns information about jobs but does not create, modify, delete, or trigger execution of any jobs. The blast radius of misuse is minimal — an agent could only gain visibility into job history or status, not cause data loss or unintended operations.
From the tool's definition Tool name 'list_generation_jobs' uses the verb 'list', which retrieves and queries data about local creative generation jobs without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
List local Raven creative generation jobs. It is categorised as a Read tool in the Raven MCP Server, which means it retrieves data without modifying state.
list_generation_jobs accepts 3 parameters: limit, status, media_type. The full parameter table on this page comes from the server's own tool schema.
Register the Raven MCP server in PolicyLayer and add a rule for list_generation_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 Raven. Nothing to install.
list_generation_jobs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_generation_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.
Set action: deny in the PolicyLayer policy for list_generation_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.
list_generation_jobs is provided by the Raven MCP server (raven-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →