AI agents call view_photos to retrieve information from Darktable without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays photo data without creating, modifying, deleting, or executing code. It is a simple read operation with minimal risk—viewing photos has no side effects on the system or data state.
From the tool's definition Tool name 'view_photos' and description 'Browse photos in the user' indicate data retrieval with no modification. 'Browse' is a read-only action.
Attacks that exploit this kind of access
Browse photos in the user. It is categorised as a Read tool in the Darktable MCP Server, which means it retrieves data without modifying state.
Register the Darktable MCP server in PolicyLayer and add a rule for view_photos: 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 Darktable. Nothing to install.
view_photos is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the view_photos 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 view_photos. 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.
view_photos is provided by the Darktable MCP server (w1ne/darktable-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →