Medium Risk

export_icon_sizes

export_icon_sizes

How to control export_icon_sizes ↓

What export_icon_sizes does on Gimp

AI agents use export_icon_sizes 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.

Medium Risk

Why export_icon_sizes needs a policy

The tool creates or writes image files in multiple icon size formats. This is a Write-category action because it generates output files that can be modified or deleted later. Severity is medium due to potential for filling storage, overwriting existing files, or resource exhaustion, but not critical since file export is a standard, reversible operation.

From the tool's definition Tool name 'export_icon_sizes' indicates image file export/output generation. Server context shows GIMP image manipulation capabilities with PyGObject API. Export operations create new files, constituting reversible Write operations.

Documented attack patterns abuse exactly the kind of access export_icon_sizes gives an agent:

How to control export_icon_sizes

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_icon_sizes:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_icon_sizes": {
      "limits": [
        {
          "counter": "export_icon_sizes_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

export_icon_sizes 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.

  1. Create a free account and register Gimp — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about export_icon_sizes

What does the export_icon_sizes tool do? +

export_icon_sizes. 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.

How do I enforce a policy on export_icon_sizes? +

Register the Gimp MCP server in PolicyLayer and add a rule for export_icon_sizes: 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.

What risk level is export_icon_sizes? +

export_icon_sizes is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit export_icon_sizes? +

Yes. Add a rate_limit block to the export_icon_sizes 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.

How do I block export_icon_sizes completely? +

Set action: deny in the PolicyLayer policy for export_icon_sizes. 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.

What MCP server provides export_icon_sizes? +

export_icon_sizes 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.

Enforce policy on every Gimp tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.