immich_assets_bulk_update · Immich MCP: Risk & Policy

WHAT IT DOES

What immich_assets_bulk_update does on Immich

AI agents use immich_assets_bulk_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.

WHY IT NEEDS A POLICY

Why immich_assets_bulk_update needs a policy

This tool creates or modifies data (metadata) for multiple assets reversibly. It falls under Write rather than Destructive because updates are reversible and the dry_run feature explicitly supports preview/validation before commitment. However, the bulk nature and lack of granular access control details elevate severity to medium—an agent could inadvertently modify metadata across many assets simultaneously.

From the tool's definition Tool name contains 'bulk_update' and description states 'Update metadata for multiple assets at once'. The 'dry_run' parameter indicates reversible modifications to asset metadata rather than destructive deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

immich_assets_bulk_update Rate-limited

immich_assets_bulk_update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "immich_assets_bulk_update": {
      "limits": [
        {
          "counter": "immich_assets_bulk_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Immich, so you can run agents against it safely.

FAQ

Questions about immich_assets_bulk_update

What does the immich_assets_bulk_update tool do? +

Update metadata for multiple assets at once. Supports dry_run to preview changes. 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.

How do I enforce a policy on immich_assets_bulk_update? +

Register the Immich MCP server in PolicyLayer and add a rule for immich_assets_bulk_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.

What risk level is immich_assets_bulk_update? +

immich_assets_bulk_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit immich_assets_bulk_update? +

Yes. Add a rate_limit block to the immich_assets_bulk_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.

How do I block immich_assets_bulk_update completely? +

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

What MCP server provides immich_assets_bulk_update? +

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