set_pick_status

Set pick flag: -1 reject, 0 unflag, 1 pick.

SERVERLightroom Classic MCP SOURCE4xiomdev/lightroom-classic-mcp

Medium RISK CLASS

Category Write

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/set-pick-status.md

WHAT IT DOES

What set_pick_status does on Lightroom Classic MCP

AI agents use set_pick_status to create or update resources in Lightroom Classic MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lightroom Classic MCP environment.

RISK

Why set_pick_status is rated Medium

The tool creates or modifies data (pick/reject flags) reversibly. It affects photo organization and selection state but does not delete data, execute code, trigger external operations, or move money. The change can be easily undone by setting a different flag value. This is characteristic of Write category operations.

From the tool's definition Tool modifies photo metadata flags (pick status: -1 reject, 0 unflag, 1 pick) in Lightroom Classic. This is a reversible metadata operation that changes organizational state without destructive consequences.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

set_pick_status Rate-limited

set_pick_status stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_pick_status": {
      "limits": [
        {
          "counter": "set_pick_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about set_pick_status

What does the set_pick_status tool do? +

Set pick flag: -1 reject, 0 unflag, 1 pick. It is categorised as a Write tool in the Lightroom Classic MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_pick_status? +

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

set_pick_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_pick_status? +

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

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

set_pick_status 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

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →