AI agents invoke open_gimp_gui to trigger actions in Inkscape. 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.
The tool name implies opening/launching the GIMP graphical application, which constitutes triggering an external operation. With no description available, confidence is reduced, but launching GUI applications can have significant system-level effects. Severity is high because an AI agent could potentially use an opened GIMP instance to manipulate files or execute further operations.
From the tool's definition Tool name 'open_gimp_gui' suggests launching an external GUI application (GIMP); description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access open_gimp_gui gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Inkscape, and nothing reaches the server without passing your rules. This is the rule we recommend for open_gimp_gui:
{
"version": "1",
"default": "deny",
"tools": {
"open_gimp_gui": {
"limits": [
{
"counter": "open_gimp_gui_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}open_gimp_gui 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.
Free to start. No card required.
open_gimp_gui. It is categorised as a Execute tool in the Inkscape MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Inkscape MCP server in PolicyLayer and add a rule for open_gimp_gui: 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 Inkscape. Nothing to install.
open_gimp_gui is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the open_gimp_gui 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 open_gimp_gui. 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.
open_gimp_gui is provided by the Inkscape MCP server (sandraschi/inkscape-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Inkscape, 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.
58 Inkscape tools catalogued and risk-classified — across an index of 43,000+ MCP servers.