remove_from_collection
Remove selected photos (or specific local_ids) from a collection.
This record as markdown: /tools/4xiomdev-lightroom-classic-mcp/remove-from-collection.md
What remove_from_collection does on Lightroom Classic MCP
AI agents call remove_from_collection 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 remove_from_collection is rated Critical
Removing photos from a collection is a destructive operation as it irreversibly removes the association between photos and the collection. While the photos themselves are not deleted, the collection membership change may not be easily reversible (no undo guarantee in automated workflows). The blast radius is medium since it affects organizational structure but not the underlying photo files.
From the tool's definition Remove selected photos (or specific local_ids) from a collection
Attacks that exploit this kind of access
The rule that runs remove_from_collection 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 remove_from_collection, this is the rule to start with:
remove_from_collection 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 remove_from_collection call is checked against it from then on.
Questions about remove_from_collection
Remove selected photos (or specific local_ids) from a collection. 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 remove_from_collection: 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.
remove_from_collection 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 remove_from_collection 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 remove_from_collection. 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.
remove_from_collection 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