AI agents use compress-image to create or update resources in MCP Media Processing Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Media Processing Server environment.
Compression is a reversible modification operation that overwrites the source image file with a compressed version. This is a Write operation because it creates or modifies data reversibly (the original uncompressed version is replaced, but compression itself is not destructive in the sense that the image content remains accessible and can be decompressed).
From the tool's definition Tool name 'compress-image' and description 'Compress PNG image using ImageMagick' indicate the tool modifies image files by reducing file size while preserving the image data.
Documented attack patterns abuse exactly the kind of access compress-image gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Media Processing Server, and nothing reaches the server without passing your rules. This is the rule we recommend for compress-image:
{
"version": "1",
"default": "deny",
"tools": {
"compress-image": {
"limits": [
{
"counter": "compress-image_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}compress-image 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.
Free to start. No card required.
Compress PNG image using ImageMagick. It is categorised as a Write tool in the MCP Media Processing Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Media Processing Server MCP server in PolicyLayer and add a rule for compress-image: 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 MCP Media Processing Server. Nothing to install.
compress-image 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 compress-image 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 compress-image. 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.
compress-image is provided by the MCP Media Processing Server MCP server (maoxiaoke/mcp-media-processor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Media Processing Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 MCP Media Processing Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.