create_snapshot
Create a named develop snapshot for the active photo.
This record as markdown: /tools/4xiomdev-lightroom-classic-mcp/create-snapshot.md
What create_snapshot does on Lightroom Classic MCP
AI agents use create_snapshot to create or update resources in Lightroom Classic MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lightroom Classic MCP environment.
Why create_snapshot is rated Medium
Snapshots in Lightroom Classic are named checkpoints of develop settings that can be freely deleted or reverted without permanent data loss. This is a reversible write operation that modifies the photo's internal state (adding a snapshot entry) rather than the underlying image file. The blast radius is minimal—misuse would only clutter the snapshot history, not cause data loss or side effects beyond Lightroom.
From the tool's definition Tool description states 'Create a named develop snapshot', which creates a new, reversible artifact (a snapshot) in Lightroom's develop history. This is not data deletion or external execution, but rather creation of a named state that can be undone.
Attacks that exploit this kind of access
The rule that runs create_snapshot 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 create_snapshot, this is the rule to start with:
create_snapshot stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Lightroom Classic MCP, apply this rule, and every create_snapshot call is checked against it from then on.
Questions about create_snapshot
Create a named develop snapshot for the active photo. It is categorised as a Write tool in the Lightroom Classic MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lightroom Classic MCP server in PolicyLayer and add a rule for create_snapshot: 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.
create_snapshot is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_snapshot 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 create_snapshot. 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.
create_snapshot 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.
This server
Across the catalogue