New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

remove_from_collection

Remove selected photos (or specific local_ids) from a collection.

SERVERLightroom Classic MCP SOURCE4xiomdev/lightroom-classic-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about remove_from_collection

What does the remove_from_collection tool do? +

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.

How do I enforce a policy on remove_from_collection? +

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.

What risk level is remove_from_collection? +

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.

Can I rate-limit remove_from_collection? +

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.

How do I block remove_from_collection completely? +

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.

What MCP server provides remove_from_collection? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Lightroom Classic's. Pull the full record:

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.