Compress and optimize images using external API (e.g., TinyPNG)
AI agents use optimize-media to create or update resources in AutoWP MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AutoWP MCP Server environment.
The tool modifies existing media by compressing and optimizing images. This is a Write operation because it creates modified versions of data (reversible transformation). Severity is medium because misuse could degrade image quality or affect site performance, but changes are generally reversible by re-uploading original media.
From the tool's definition Tool description states 'Compress and optimize images using external API' — this modifies media files (compresses/optimizes them) which is a reversible alteration to WordPress media library content.
Documented attack patterns abuse exactly the kind of access optimize-media gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AutoWP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for optimize-media:
{
"version": "1",
"default": "deny",
"tools": {
"optimize-media": {
"limits": [
{
"counter": "optimize-media_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}optimize-media 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 and optimize images using external API (e.g., TinyPNG). It is categorised as a Write tool in the AutoWP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AutoWP MCP Server MCP server in PolicyLayer and add a rule for optimize-media: 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 AutoWP MCP Server. Nothing to install.
optimize-media 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 optimize-media 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 optimize-media. 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.
optimize-media is provided by the AutoWP MCP Server MCP server (njengah/autowpmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AutoWP MCP 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.
47 AutoWP MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.