lightroom_status

Get plugin status, command count, and socket state.

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

WHAT IT DOES

What lightroom_status does on Lightroom Classic MCP

AI agents call lightroom_status 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 lightroom_status is rated Low

This tool only retrieves and reports diagnostic/status information about the Lightroom plugin itself (plugin status, command count, socket state). It performs no modifications, deletions, executions, or financial operations. It is a simple inspection tool with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'lightroom_status' and description 'Get plugin status, command count, and socket state' indicate read-only query operations that retrieve status information without modifying any data or triggering side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

lightroom_status Allowed

lightroom_status 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": {
    "lightroom_status": {}
  }
}

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

FAQ

Questions about lightroom_status

What does the lightroom_status tool do? +

Get plugin status, command count, and socket state. 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 lightroom_status? +

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

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

Can I rate-limit lightroom_status? +

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

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

lightroom_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

editor_status on 010 Editor → The MCP Attack Database →

Guides

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