AI agents use select_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.
In GIMP, 'select_ellipse' creates an elliptical selection on the canvas. This modifies the selection state of the image (a reversible write operation) but does not execute code, delete data, or involve financial transactions. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'select_ellipse' on a GIMP MCP server; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access select_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 select_ellipse:
{
"version": "1",
"default": "deny",
"tools": {
"select_ellipse": {
"limits": [
{
"counter": "select_ellipse_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}select_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.
select_ellipse. 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 select_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.
select_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 select_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 select_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.
select_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.