Set properties on an existing layer. Parameters: - layer_name / layer_index: Identify the layer (defaults to active layer) - opacity: New opacity 0-100 (omit to leave unchanged) - blend_mode: New GIMP layer mode name (omit to leave unchanged) - visible: True/False visibility (omit to leave unchan...
AI agents use set_layer_properties 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 modifies layer properties (opacity, blend mode, visibility) which are core image editing operations. While these changes are reversible and don't delete data, they constitute write operations that alter the image composition. The severity is medium because misuse could degrade image quality or produce unwanted visual effects, but the changes can be undone via GIMP's undo functionality.
From the tool's definition Tool description states it 'Set properties on an existing layer' with parameters to modify opacity, blend_mode, and visibility. These are reversible modifications to layer state in GIMP.
Documented attack patterns abuse exactly the kind of access set_layer_properties 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_layer_properties:
{
"version": "1",
"default": "deny",
"tools": {
"set_layer_properties": {
"limits": [
{
"counter": "set_layer_properties_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_layer_properties 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.
Set properties on an existing layer. Parameters: - layer_name / layer_index: Identify the layer (defaults to active layer) - opacity: New opacity 0-100 (omit to leave unchanged) - blend_mode: New GIMP layer mode name (omit to leave unchanged) - visible: True/False visibility (omit to leave unchanged) - 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 set_layer_properties: 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_layer_properties 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 set_layer_properties 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_layer_properties. 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_layer_properties 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.