AI agents use convert_and_resize 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.
This tool creates or modifies image data by converting formats and resizing dimensions. These are reversible operations—the original image is not deleted, and new versions can be regenerated or deleted. It does not execute arbitrary code, delete data irreversibly, or perform financial operations. The local execution with no uploads minimizes blast radius.
From the tool's definition Tool performs 'convert' and 'resize' operations on images, creating modified versions of image files. The description states it converts image format and resizes in 'a single operation', indicating data transformation and creation of new image outputs.
Attacks that exploit this kind of access
Convert an image to a new format and resize it in a single operation. 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.
Register the Imagic MCP server in PolicyLayer and add a rule for convert_and_resize: 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.
convert_and_resize 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 convert_and_resize 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 convert_and_resize. 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.
convert_and_resize 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.
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 →