merge_images · Imagic MCP: Risk & Policy

WHAT IT DOES

What merge_images does on Imagic

AI agents use merge_images to create or update resources in Imagic — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Imagic environment.

WHY IT NEEDS A POLICY

Why merge_images needs a policy

This tool creates or modifies image data by combining multiple images into a single output file. It is a reversible write operation (the original images remain unchanged, and the merged result can be deleted or regenerated). It does not execute arbitrary code, delete data irreversibly, or move money. The local-only operation and non-destructive nature keep severity low.

From the tool's definition Tool description states it 'Merge[s] multiple images into a single image' — a creation/modification operation that produces new image output.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

merge_images Rate-limited

merge_images 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": {
    "merge_images": {
      "limits": [
        {
          "counter": "merge_images_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 Imagic, so you can run agents against it safely.

FAQ

Questions about merge_images

What does the merge_images tool do? +

Merge multiple images into a single image by arranging them horizontally, vertically, or in a grid. It is categorised as a Write tool in the Imagic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on merge_images? +

Register the Imagic MCP server in PolicyLayer and add a rule for merge_images: 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 Imagic. Nothing to install.

What risk level is merge_images? +

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

Can I rate-limit merge_images? +

Yes. Add a rate_limit block to the merge_images 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 merge_images completely? +

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

merge_images is provided by the Imagic MCP server (sonic0002/imagic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.