Process multiple RAW files with the same PP3 profile.
AI agents invoke batch_process to trigger actions in Rawtherapee. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool runs the RawTherapee CLI to process multiple RAW photo files, which constitutes executing an external operation. The blast radius is high because it operates on multiple files simultaneously, potentially overwriting or generating numerous output files. It is not Destructive in the irreversible-deletion sense, but it does execute batch external operations whose effects depend on the arguments provided.
From the tool's definition 'Process multiple RAW files with the same PP3 profile' — triggers RawTherapee CLI execution across multiple files
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Process multiple RAW files with the same PP3 profile. It is categorised as a Execute tool in the Rawtherapee MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Rawtherapee MCP server in PolicyLayer and add a rule for batch_process: 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 Rawtherapee. Nothing to install.
batch_process is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the batch_process 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 batch_process. 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.
batch_process is provided by the Rawtherapee MCP server (lucamarien/rawtherapee-mcp-server). 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 →