apply_lut
AI agents invoke apply_lut 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.
Applying a LUT to an image is a processing/transformation operation that modifies image rendering through RawTherapee CLI execution. It is not purely reading data, and given the server context of RAW photo development via CLI, this likely triggers an external operation. With no description, confidence is reduced, but 'apply' in context of image processing tools on this server suggests Execute-level action.
From the tool's definition Tool name 'apply_lut' suggests applying a Look-Up Table (LUT) to an image for color grading/transformation. Description is empty, lowering confidence.
Attacks that exploit this kind of access
apply_lut. 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 apply_lut: 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.
apply_lut 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 apply_lut 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 apply_lut. 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.
apply_lut 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 →