Fill an elliptical region with a solid color. Parameters: - x, y: Top-left corner of the bounding box - width, height: Bounding box dimensions - color: Fill color (CSS name, hex, or rgb() string) - layer_name: Target layer; defaults to active layer - image_index: Target image index (default 0) Re...
AI agents use fill_ellipse 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 or modifies pixel data within a defined elliptical area on a layer. The operation is reversible through standard undo functionality (typical in image editors like GIMP), making it a Write operation rather than Destructive. The blast radius is low because it affects only a localized region of an image and causes no external side effects, data loss, or financial impact.
From the tool's definition Tool modifies image data by filling an elliptical region with a solid color. The description states it will 'Fill an elliptical region with a solid color' and returns a status dict, indicating a reversible image modification operation.
Documented attack patterns abuse exactly the kind of access fill_ellipse 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 fill_ellipse:
{
"version": "1",
"default": "deny",
"tools": {
"fill_ellipse": {
"limits": [
{
"counter": "fill_ellipse_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}fill_ellipse 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.
Fill an elliptical region with a solid color. Parameters: - x, y: Top-left corner of the bounding box - width, height: Bounding box dimensions - color: Fill color (CSS name, hex, or rgb() string) - layer_name: Target layer; defaults to active layer - image_index: Target image index (default 0) Returns status dict. 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 fill_ellipse: 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.
fill_ellipse 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 fill_ellipse 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 fill_ellipse. 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.
fill_ellipse 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.