AI agents use export_image 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.
The export_image tool writes image data to a file, which is a reversible Write operation (the resulting file can be deleted or modified later). It is not Destructive because export creates new output rather than irreversibly deleting or overwriting existing data. Severity is medium because unintended image exports could clutter the filesystem or expose sensitive edited images, but effects are recoverable.
From the tool's definition Tool name 'export_image' indicates writing/saving image data to output format. Server description states it 'enables conversational image editing' and 'exposes GIMP's full PyGObject API'. Export operations create or modify files on disk.
Documented attack patterns abuse exactly the kind of access export_image 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_image:
{
"version": "1",
"default": "deny",
"tools": {
"export_image": {
"limits": [
{
"counter": "export_image_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_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.
export_image. 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_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 Gimp. Nothing to install.
export_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 export_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 export_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.
export_image 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.