lightroom_list_commands

List command names currently exposed by the Lightroom plugin.

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/lightroom-list-commands.md

WHAT IT DOES

What lightroom_list_commands does on Lightroom Classic MCP

AI agents call lightroom_list_commands 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 lightroom_list_commands is rated Low

This tool performs a read-only enumeration of available commands. It has no side effects on photos, catalog state, or Lightroom's configuration. The blast radius of misuse is minimal—an agent could only learn what commands exist, not execute them or modify data. This is a standard introspection capability with no destructive, financial, or execution impact.

From the tool's definition Tool name 'lightroom_list_commands' and description 'List command names currently exposed by the Lightroom plugin' indicate a retrieval operation that queries available commands without modifying any data or triggering external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs lightroom_list_commands 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 lightroom_list_commands, this is the rule to start with:

lightroom_list_commands Allowed

lightroom_list_commands 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": {
    "lightroom_list_commands": {}
  }
}

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 lightroom_list_commands call is checked against it from then on.

FAQ

Questions about lightroom_list_commands

What does the lightroom_list_commands tool do? +

List command names currently exposed by the Lightroom plugin. 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 lightroom_list_commands? +

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

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

Can I rate-limit lightroom_list_commands? +

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

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

lightroom_list_commands 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 →