auto_tone

Run Auto Tone style adjustments for selected photos or local_ids.

SERVERLightroom Classic MCP SOURCE4xiomdev/lightroom-classic-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/4xiomdev-lightroom-classic-mcp/auto-tone.md

WHAT IT DOES

What auto_tone does on Lightroom Classic MCP

AI agents invoke auto_tone to trigger actions in Lightroom Classic MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why auto_tone is rated High

This tool executes Lightroom's built-in Auto Tone operation, which automatically adjusts exposure, contrast, and other tonal parameters. While the changes are reversible (Lightroom supports undo operations as evidenced by the sibling tool 'can_undo'), the tool performs a computational operation triggered by the AI agent.

From the tool's definition The tool description states it will 'Run Auto Tone style adjustments' on photos, which is an action that executes Lightroom's automatic adjustment algorithm on image data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

auto_tone Rate-limited

auto_tone stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "auto_tone": {
      "limits": [
        {
          "counter": "auto_tone_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT 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 auto_tone call is checked against it from then on.

FAQ

Questions about auto_tone

What does the auto_tone tool do? +

Run Auto Tone style adjustments for selected photos or local_ids. It is categorised as a Execute tool in the Lightroom Classic MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on auto_tone? +

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

auto_tone is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit auto_tone? +

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

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

auto_tone 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →