// SCAN REPORT

Lightroom Classic MCP

59 tools. 38 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated: 4 Oct 2026

38 can modify or destroy data

21 read-only

59 tools total

Community server · catalogue entry checked 01/10/2026

How to control Lightroom Classic MCP ↓

TOOL MAP

What Lightroom Classic MCP exposes to your agents

Read (21) Write / Execute (34) Destructive / Financial (4)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Lightroom Classic MCP tools

Destructive · High delete_collection This tool irreversibly removes a collection and its associated metadata/organization structure. Destructive · High delete_snapshot This tool permanently removes a snapshot (a saved editing state) from Lightroom's catalog. Destructive · Medium remove_from_collection Removing photos from a collection is a destructive operation as it irreversibly removes the association between photos and the collection. Destructive · High reset_current_photo Resetting all develop adjustments irreversibly removes all editing work done on a photo.

38 of Lightroom Classic MCP's 59 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Lightroom Classic MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and Lightroom Classic MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_collection": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_keywords": {
    "limits": [
      {
        "counter": "add_keywords_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "can_undo": {
    "limits": [
      {
        "counter": "can_undo_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Lightroom Classic MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON LIGHTROOM CLASSIC →

Instant setup, no code required.

FULL CATALOGUE

All 59 Lightroom Classic MCP tools

DESTRUCTIVE 4 tools

Destructive delete_collection Delete a collection by its ID. Destructive delete_snapshot Delete a develop snapshot by its ID. Destructive remove_from_collection Remove selected photos (or specific local_ids) from a collection. Destructive reset_current_photo Reset all develop adjustments on the currently active photo.

EXECUTE 5 tools

Execute auto_tone Run Auto Tone style adjustments for selected photos or local_ids. Execute select_mask_tool Select a mask tool: brush, graduated-filter, radial-filter, or range-mask. Execute send_raw_lightroom_command Send a raw command to the plugin (advanced/debug use). Execute toggle_lens_blur_depth_viz Toggle the lens blur depth visualization overlay. Execute toggle_mask_overlay Toggle the mask overlay visualization on/off.

WRITE 29 tools

Write add_keywords Add keywords (supports hierarchical format: A > B > C). Write add_to_collection Add selected photos (or specific local_ids) to a collection. Write apply_develop_preset Apply a named preset with optional parameter overrides. Write apply_develop_settings apply_develop_settings Write apply_lightroom_preset Apply a Lightroom develop preset by its UUID. Write apply_local_adjustment_settings Set local_ adjustment parameters on the currently active mask. Write apply_snapshot Apply a develop snapshot by its ID. Write auto_white_balance Set white balance to Auto for selected photos or local_ids. Write batch_apply_develop_operations batch_apply_develop_operations Write create_ai_mask Create an AI-powered mask on the active photo. Write create_collection Create a new collection (optionally inside a collection set). Write create_snapshot Create a named develop snapshot for the active photo. Write create_virtual_copy Create virtual copies of selected photos or specific local_ids. Write export_photos Export photos as JPG to a destination folder. Write invert_mask Invert the active mask (or a specific mask by ID). Write redo Redo the last undone Lightroom operation. Write remove_keywords Remove keywords by name/path from selected photos or local_ids. Write rotate_left Rotate selected photos 90 degrees left. Write rotate_right Rotate selected photos 90 degrees right. Write select_mask Select an existing mask by its numeric ID. Write set_caption Set Lightroom caption metadata for selected photos or local_ids. Write set_develop_group Apply a partial update to one develop parameter group. Write set_develop_param Set a single develop parameter across selected photos or local_ids. Write set_label Set Lightroom color label name (or empty string to clear). Write set_lens_blur_bokeh Set the lens blur bokeh shape. Write set_pick_status Set pick flag: -1 reject, 0 unflag, 1 pick. Write set_rating Set Lightroom star rating (0..5). Write set_title Set Lightroom title metadata for selected photos or local_ids. Write undo Undo the last Lightroom operation.

READ 21 tools

Read can_undo Check if undo/redo operations are available. Read find_photo_by_path Find one Lightroom catalog photo by absolute file path. Read get_active_photo Get the active Lightroom photo in the current selection. Read get_active_photo_file Get active photo metadata plus direct file-inspection details. Read get_develop_group_settings Get only the settings for one named develop group. Read get_develop_param_range Get slider range for a develop parameter (when Lightroom can report it). Read get_develop_settings get_develop_settings Read get_local_adjustment_settings Read local_ adjustment parameters on the currently active mask. Read get_selected_photo_files List selected Lightroom photos with direct file-inspection details. Read get_selected_photos List selected Lightroom photos with IDs and key metadata. Read lightroom_list_commands List command names currently exposed by the Lightroom plugin. Read lightroom_ping Verify Lightroom bridge connectivity and plugin health. Read lightroom_status Get plugin status, command count, and socket state. Read list_collections List all collections and collection sets in the catalog. Read list_develop_groups List grouped develop parameter sets for faster targeted edits. Read list_develop_param_ranges Get numeric ranges for known develop parameters (where available). Read list_develop_parameters List develop parameters known by this Lightroom Classic install. Read list_develop_presets List built-in editing presets that can be applied in one call. Read list_lightroom_presets List Lightroom's built-in and user-created develop presets. Read list_local_params List available local_ adjustment parameters for masks. Read list_snapshots List develop snapshots for the active photo.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Lightroom Classic MCP

Can an AI agent delete data through the Lightroom Classic MCP server? +

Yes. The Lightroom Classic MCP server exposes 4 destructive tools including delete_collection, delete_snapshot, remove_from_collection. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Lightroom Classic MCP? +

The Lightroom Classic MCP server has 29 write tools including add_keywords, add_to_collection, apply_develop_preset. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Lightroom Classic MCP.

How many tools does the Lightroom Classic MCP server expose? +

59 tools across 4 categories: Destructive, Execute, Read, Write. 21 are read-only. 38 can modify, create, or delete data.

How do I enforce a policy on Lightroom Classic MCP? +

Register the Lightroom Classic MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Lightroom Classic MCP tool call.

Deterministic rules across all 59 Lightroom Classic MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON LIGHTROOM CLASSIC →

Instant setup, no code required.

59 Lightroom Classic MCP tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Lightroom Classic's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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