check_lens_support
AI agents call check_lens_support to retrieve information from Rawtherapee without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve or query lens support information from RawTherapee, which is a non-destructive read operation. No data modification, code execution, deletion, or financial transaction is implied. The name convention ('check_*') strongly suggests a query or validation function.
From the tool's definition Tool name 'check_lens_support' implies querying or verifying lens compatibility data without modifying anything. Description is empty, but the semantic meaning of 'check' is to inspect or retrieve information.
Attacks that exploit this kind of access
check_lens_support. It is categorised as a Read tool in the Rawtherapee MCP Server, which means it retrieves data without modifying state.
Register the Rawtherapee MCP server in PolicyLayer and add a rule for check_lens_support: 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.
check_lens_support 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 check_lens_support 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 check_lens_support. 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.
check_lens_support 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 →