Export an image as both JPEG and PNG, choosing the smaller format. Parameters: - output_dir: Directory to write output files - jpeg_quality: JPEG quality 1-100 (default 85) - png_compression: PNG compression level 0-9 (default 9) - max_width / max_height: Optional scaling before export - image_in...
AI agents use export_web_optimized to create or update resources in Gimp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gimp environment.
This tool creates new files (JPEG and PNG exports) in a specified directory, which is a Write operation—it modifies the filesystem with new data. While reversible (exported files can be deleted), it still constitutes data creation.
From the tool's definition Tool description states 'Export an image as both JPEG and PNG' and 'output_dir: Directory to write output files', indicating file creation operations. The return value includes 'jpeg_path' and 'png_path', confirming files are written to the filesystem.
Documented attack patterns abuse exactly the kind of access export_web_optimized gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gimp, and nothing reaches the server without passing your rules. This is the rule we recommend for export_web_optimized:
{
"version": "1",
"default": "deny",
"tools": {
"export_web_optimized": {
"limits": [
{
"counter": "export_web_optimized_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_web_optimized 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.
Export an image as both JPEG and PNG, choosing the smaller format. Parameters: - output_dir: Directory to write output files - jpeg_quality: JPEG quality 1-100 (default 85) - png_compression: PNG compression level 0-9 (default 9) - max_width / max_height: Optional scaling before export - image_index: Source image index (default 0) Returns: {jpeg_path, jpeg_size, png_path, png_size, recommendation}. It is categorised as a Write tool in the Gimp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gimp MCP server in PolicyLayer and add a rule for export_web_optimized: 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 Gimp. Nothing to install.
export_web_optimized 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 export_web_optimized 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 export_web_optimized. 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.
export_web_optimized is provided by the Gimp MCP server (maorcc/gimp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gimp, 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.
79 Gimp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.