High Risk →

scale_image

scale_image

How to control scale_image ↓

What scale_image does on Gimp

AI agents invoke scale_image to trigger actions in Gimp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Why scale_image needs a policy

Scaling images in GIMP is an Execute action—it runs an image processing operation with effects contingent on supplied parameters (width, height, interpolation mode). While the operation is reversible (unlike Destructive), it triggers external GIMP processes whose outcomes depend entirely on how an AI agent configures the arguments.

From the tool's definition The tool name 'scale_image' on a GIMP-bridging MCP server that 'exposes GIMP's full PyGObject API for AI-powered image manipulation' indicates execution of image transformation operations.

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

How to control scale_image

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "scale_image": {
      "limits": [
        {
          "counter": "scale_image_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

scale_image stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about scale_image

What does the scale_image tool do? +

scale_image. It is categorised as a Execute tool in the Gimp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on scale_image? +

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

What risk level is scale_image? +

scale_image is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit scale_image? +

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

How do I block scale_image completely? +

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

What MCP server provides scale_image? +

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

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.