Raise a specific image to the front / make it active in GIMP. Parameters: - image_index: Index of the image to activate (from list_images) Returns status dict.
AI agents invoke set_active_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.
This tool performs an action in the GIMP application (changing the active/focused image), which is an external operation that affects application state. It doesn't read data, write/modify image content, or destroy anything, but it does trigger a UI/state change in an external program, making Execute the most appropriate category.
From the tool's definition 'Raise a specific image to the front / make it active in GIMP' — triggers an external operation in the GIMP application, changing its UI state
Documented attack patterns abuse exactly the kind of access set_active_image 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 set_active_image:
{
"version": "1",
"default": "deny",
"tools": {
"set_active_image": {
"limits": [
{
"counter": "set_active_image_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}set_active_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.
Free to start. No card required.
Raise a specific image to the front / make it active in GIMP. Parameters: - image_index: Index of the image to activate (from list_images) Returns status dict. 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.
Register the Gimp MCP server in PolicyLayer and add a rule for set_active_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.
set_active_image 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 set_active_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.
Set action: deny in the PolicyLayer policy for set_active_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.
set_active_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.
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.