add_luminance_adjustment
AI agents use add_luminance_adjustment to create or update resources in Rawtherapee — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rawtherapee environment.
The tool modifies image data (luminance channel) reversibly as part of a RAW photo editing workflow. This is a Write operation rather than Execute because it applies a specific parameter adjustment rather than executing arbitrary code. It is not Destructive because luminance adjustments in RAW editors are non-destructive and can be undone.
From the tool's definition Tool name 'add_luminance_adjustment' indicates modification of image luminance values. Server context shows this is part of RawTherapee CLI photo development workflow where tools like 'adjust_crop_position', 'adjust_profile', and 'apply_local_preset' all…
Attacks that exploit this kind of access
add_luminance_adjustment. It is categorised as a Write tool in the Rawtherapee MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rawtherapee MCP server in PolicyLayer and add a rule for add_luminance_adjustment: 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.
add_luminance_adjustment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_luminance_adjustment 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 add_luminance_adjustment. 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.
add_luminance_adjustment 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 →