Move a layer to a new stack position. Parameters: - new_position: Target stack index (0 = bottom) - layer_name / layer_index: Identify the layer (defaults to active layer) - image_index: Target image index (default 0) Returns status dict.
AI agents use reorder_layer 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 image data structure reversibly by reordering layers. While it changes the image, the operation is fully reversible (layers can be reordered back), distinguishing it from Destructive actions. It does not delete data, execute arbitrary code, or trigger external side effects beyond GIMP's layer management.
From the tool's definition Tool description states "Move a layer to a new stack position" which modifies the layer ordering within an image. Parameters include new_position and layer identification, enabling structural changes to image composition.
Documented attack patterns abuse exactly the kind of access reorder_layer 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 reorder_layer:
{
"version": "1",
"default": "deny",
"tools": {
"reorder_layer": {
"limits": [
{
"counter": "reorder_layer_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}reorder_layer 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.
Move a layer to a new stack position. Parameters: - new_position: Target stack index (0 = bottom) - layer_name / layer_index: Identify the 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 reorder_layer: 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.
reorder_layer 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 reorder_layer 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 reorder_layer. 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.
reorder_layer 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.