list_batch_jobs
AI agents call list_batch_jobs to retrieve information from MCP Mistral OCR Optimized without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries existing batch job information to retrieve their status and details. It has no side effects—it only fetches data about previously created jobs. The empty description lowers confidence slightly, but the naming convention and context of sibling batch management tools strongly indicate a data retrieval function rather than creation, modification, or deletion.
From the tool's definition Tool name 'list_batch_jobs' combined with sibling tools like 'check_batch_status', 'download_batch_results', and 'process_batch_local_files' indicates this retrieves job metadata without modification. The verb 'list' is a classic Read operation pattern.
Attacks that exploit this kind of access
list_batch_jobs. It is categorised as a Read tool in the MCP Mistral OCR Optimized MCP Server, which means it retrieves data without modifying state.
Register the MCP Mistral OCR Optimized MCP server in PolicyLayer and add a rule for list_batch_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 Mistral OCR Optimized. Nothing to install.
list_batch_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_batch_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_batch_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_batch_jobs is provided by the MCP Mistral OCR Optimized MCP server (snussik/mcp_mistral_ocr_opt). 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 →