list_develop_parameters

List develop parameters known by this Lightroom Classic install.

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/list-develop-parameters.md

WHAT IT DOES

What list_develop_parameters does on Lightroom Classic MCP

AI agents call list_develop_parameters 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.

RISK

Why list_develop_parameters is rated Low

This tool retrieves metadata about Lightroom Classic's available develop parameters. It has no capability to modify photos, apply settings, delete data, or execute arbitrary code. The worst outcome of misuse is information disclosure about what parameters are available, which has minimal security impact. This is a straightforward read operation querying configuration/capability information.

From the tool's definition Tool name 'list_develop_parameters' and description 'List develop parameters known by this Lightroom Classic install' indicate a query/retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_develop_parameters safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Lightroom Classic MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_develop_parameters, this is the rule to start with:

list_develop_parameters Allowed

list_develop_parameters is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_develop_parameters": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Lightroom Classic MCP, apply this rule, and every list_develop_parameters call is checked against it from then on.

FAQ

Questions about list_develop_parameters

What does the list_develop_parameters tool do? +

List develop parameters known by this Lightroom Classic install. 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 list_develop_parameters? +

Register the Lightroom Classic MCP server in PolicyLayer and add a rule for list_develop_parameters: 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 list_develop_parameters? +

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

Can I rate-limit list_develop_parameters? +

Yes. Add a rate_limit block to the list_develop_parameters 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 list_develop_parameters completely? +

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

list_develop_parameters 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.

KEEP EXPLORING

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

This server

All 59 Lightroom Classic tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →