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

reset_current_photo

Reset all develop adjustments on the currently active photo.

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/reset-current-photo.md

What reset_current_photo does on Lightroom Classic MCP

AI agents call reset_current_photo 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 reset_current_photo is rated Critical

Resetting all develop adjustments irreversibly removes all editing work done on a photo. While Lightroom Classic does maintain a history, the tool as described performs a bulk reset of all adjustments which is a destructive, hard-to-recover action for professional photo editing workflows. The word 'reset' combined with 'all develop adjustments' indicates complete overwrite of prior editing state.

From the tool's definition Reset all develop adjustments on the currently active photo

Questions about reset_current_photo

What does the reset_current_photo tool do? +

Reset all develop adjustments on the currently active photo. 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 reset_current_photo? +

Register the Lightroom Classic MCP server in PolicyLayer and add a rule for reset_current_photo: 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 reset_current_photo? +

reset_current_photo 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 reset_current_photo? +

Yes. Add a rate_limit block to the reset_current_photo 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 reset_current_photo completely? +

Set action: deny in the PolicyLayer policy for reset_current_photo. 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 reset_current_photo? +

reset_current_photo 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.