This record as markdown: /tools/mukul975-mcp-windows-automation/last-photo.md
What last_photo does on Mcp Windows
AI agents invoke last_photo to trigger actions in Mcp Windows. 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 last_photo is rated High
This tool triggers a navigation action within Adobe Lightroom (an external application), causing a UI interaction/browser-style action. It executes an operation in an external application rather than simply reading or writing data. The blast radius is medium as it changes application state but doesn't destroy data.
From the tool's definition Go to last photo in Lightroom
Attacks that exploit this kind of access
The rule that runs last_photo safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Windows, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For last_photo, this is the rule to start with:
last_photo 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Windows, apply this rule, and every last_photo call is checked against it from then on.
Questions about last_photo
Go to last photo in Lightroom. It is categorised as a Execute tool in the Mcp Windows MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Windows MCP server in PolicyLayer and add a rule for last_photo: 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 Mcp Windows. Nothing to install.
last_photo is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the last_photo 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.
Set action: deny in the PolicyLayer policy for last_photo. 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.
last_photo is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Windows, and thousands of servers like it.
Across the catalogue