can_undo

Check if undo/redo operations are available.

SERVERLightroom Classic MCP SOURCE4xiomdev/lightroom-classic-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/4xiomdev-lightroom-classic-mcp/can-undo.md

WHAT IT DOES

What can_undo does on Lightroom Classic MCP

AI agents call can_undo to retrieve information from Lightroom Classic MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why can_undo is rated Low

This tool only queries the availability of undo/redo operations without performing any action. It reads state information and has no side effects.

From the tool's definition Check if undo/redo operations are available

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs can_undo 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 can_undo, this is the rule to start with:

can_undo Allowed

can_undo is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "can_undo": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Lightroom Classic MCP, apply this rule, and every can_undo call is checked against it from then on.

FAQ

Questions about can_undo

What does the can_undo tool do? +

Check if undo/redo operations are available. It is categorised as a Read tool in the Lightroom Classic MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on can_undo? +

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

can_undo is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit can_undo? +

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

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

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

KEEP EXPLORING

More on Lightroom Classic, and thousands of servers like it.

This server

All 59 Lightroom Classic tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →