delete_snapshot
Delete a develop snapshot by its ID.
This record as markdown: /tools/4xiomdev-lightroom-classic-mcp/delete-snapshot.md
What delete_snapshot does on Lightroom Classic MCP
AI agents call delete_snapshot to permanently remove resources in Lightroom Classic MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_snapshot is rated Critical
This tool permanently removes a snapshot (a saved editing state) from Lightroom's catalog. Snapshots cannot be restored after deletion, making this a destructive operation. While the blast radius is somewhat contained to a single snapshot rather than bulk data, the irreversible nature and lack of undo capability places it in the Destructive category rather than Write.
From the tool's definition Tool name is 'delete_snapshot' with description 'Delete a develop snapshot by its ID.' The verb 'Delete' combined with 'by its ID' indicates irreversible removal of data. Snapshots in Lightroom are non-recoverable editing states once deleted.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_snapshot, this is the rule to start with:
delete_snapshot is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Lightroom Classic MCP, apply this rule, and every delete_snapshot call is checked against it from then on.
Questions about delete_snapshot
Delete a develop snapshot by its ID. It is categorised as a Destructive tool in the Lightroom Classic MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Lightroom Classic MCP server in PolicyLayer and add a rule for delete_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.
delete_snapshot is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue