AI agents use immich_assets_update to create or update resources in Immich — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Immich environment.
This tool modifies asset metadata (favorite status, archive state, description, rating) which are reversible changes. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or involve financial transactions (would be Financial). The severity is medium because malicious updates could alter user data organization and tagging, but changes are easily reversible.
From the tool's definition Tool name 'immich_assets_update' and description 'Update metadata for a single asset (favorite, archived, description, rating)' indicate modification of asset properties without deletion or irreversible destruction.
Attacks that exploit this kind of access
Update metadata for a single asset (favorite, archived, description, rating). It is categorised as a Write tool in the Immich MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Immich MCP server in PolicyLayer and add a rule for immich_assets_update: 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 Immich. Nothing to install.
immich_assets_update 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 immich_assets_update 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 immich_assets_update. 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.
immich_assets_update is provided by the Immich MCP server (whitehara/immich-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 →