AI agents use apply_ratings_batch to create or update resources in Darktable — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Darktable environment.
The tool creates or modifies metadata files (XMP sidecars) associated with images, which is a reversible write operation. While it affects multiple files in batch, the changes are metadata-only and can be undone (ratings can be modified or removed). This is less severe than destructive operations but more impactful than simple reads due to batch scope and file modification.
From the tool's definition The tool writes XMP sidecars containing rating metadata (xmp:Rating) for a batch of photos. This is a create/modify operation that persists data to files.
Attacks that exploit this kind of access
Write XMP sidecars (xmp:Rating) for a batch of. It is categorised as a Write tool in the Darktable MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Darktable MCP server in PolicyLayer and add a rule for apply_ratings_batch: 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.
apply_ratings_batch is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the apply_ratings_batch 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 apply_ratings_batch. 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.
apply_ratings_batch 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 →