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

send_raw_lightroom_command

Send a raw command to the plugin (advanced/debug use).

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/send-raw-lightroom-command.md

What send_raw_lightroom_command does on Lightroom Classic MCP

AI agents invoke send_raw_lightroom_command 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.

Why send_raw_lightroom_command is rated High

Sending raw/arbitrary commands to a plugin bridge is an Execute-category action. The tool is explicitly labeled for advanced/debug use, implying it can trigger a wide range of operations depending on the command payload, potentially spanning read, write, or destructive actions.

From the tool's definition 'Send a raw command to the plugin (advanced/debug use)' — executes arbitrary raw commands against the Lightroom plugin bridge

Questions about send_raw_lightroom_command

What does the send_raw_lightroom_command tool do? +

Send a raw command to the plugin (advanced/debug use). 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 send_raw_lightroom_command? +

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

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

Can I rate-limit send_raw_lightroom_command? +

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

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

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