New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_develop_param_range

Get slider range for a develop parameter (when Lightroom can report it).

SERVERLightroom Classic MCP SOURCE4xiomdev/lightroom-classic-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/4xiomdev-lightroom-classic-mcp/get-develop-param-range.md

What get_develop_param_range does on Lightroom Classic MCP

AI agents call get_develop_param_range to retrieve information from Lightroom Classic MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_develop_param_range is rated Low

This tool retrieves information about the valid range of a develop parameter slider in Lightroom Classic. It performs a read-only query to report metadata (min/max values or bounds) for UI or validation purposes. There are no side effects, no data modification, no execution of external commands, and no destructive operations.

From the tool's definition Tool name 'get_develop_param_range' and description 'Get slider range for a develop parameter' indicate a retrieval operation that queries metadata about available parameter ranges without modifying any data or triggering external operations.

Questions about get_develop_param_range

What does the get_develop_param_range tool do? +

Get slider range for a develop parameter (when Lightroom can report it). It is categorised as a Read tool in the Lightroom Classic MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_develop_param_range? +

Register the Lightroom Classic MCP server in PolicyLayer and add a rule for get_develop_param_range: 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 Lightroom Classic MCP. Nothing to install.

What risk level is get_develop_param_range? +

get_develop_param_range is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_develop_param_range? +

Yes. Add a rate_limit block to the get_develop_param_range 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.

How do I block get_develop_param_range completely? +

Set action: deny in the PolicyLayer policy for get_develop_param_range. 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.

What MCP server provides get_develop_param_range? +

get_develop_param_range is provided by the Lightroom Classic MCP server (4xiomdev/lightroom-classic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Lightroom Classic, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Lightroom Classic's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.