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

toggle_lens_blur_depth_viz

Toggle the lens blur depth visualization overlay.

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/toggle-lens-blur-depth-viz.md

What toggle_lens_blur_depth_viz does on Lightroom Classic MCP

AI agents invoke toggle_lens_blur_depth_viz 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 toggle_lens_blur_depth_viz is rated High

This tool triggers a UI state change in Lightroom Classic — toggling a visualization overlay on or off. It doesn't read data, write/modify photo settings persistently, or delete anything. It executes an application action (toggling a display mode), making Execute the most appropriate category. Severity is low since it only affects a visual overlay with no persistent data changes.

From the tool's definition Toggle the lens blur depth visualization overlay

Questions about toggle_lens_blur_depth_viz

What does the toggle_lens_blur_depth_viz tool do? +

Toggle the lens blur depth visualization overlay. 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 toggle_lens_blur_depth_viz? +

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

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

Can I rate-limit toggle_lens_blur_depth_viz? +

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

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

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