Draw an ellipse outline (stroke only) on a layer. Parameters: - x, y: Top-left corner of the bounding box - width, height: Bounding box dimensions - color: Stroke color; uses current foreground if omitted - line_width: Stroke width in pixels (default 2.0) - layer_name: Target layer; defaults to a...
AI agents use draw_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 new graphical content (an ellipse stroke) on an image layer, which is a reversible modification of image data. It does not execute arbitrary code, delete data, or access external systems. The modification can be undone in GIMP, making it a Write operation rather than Execute or Destructive.
From the tool's definition Tool name 'draw_ellipse' combined with description stating it 'Draw[s] an ellipse outline (stroke only) on a layer' with parameters for positioning, dimensions, color, and line width. This creates/modifies pixel data on an image layer.
Documented attack patterns abuse exactly the kind of access draw_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 draw_ellipse:
{
"version": "1",
"default": "deny",
"tools": {
"draw_ellipse": {
"limits": [
{
"counter": "draw_ellipse_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}draw_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.
Draw an ellipse outline (stroke only) on a layer. Parameters: - x, y: Top-left corner of the bounding box - width, height: Bounding box dimensions - color: Stroke color; uses current foreground if omitted - line_width: Stroke width in pixels (default 2.0) - 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 draw_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.
draw_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 draw_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 draw_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.
draw_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.