adjust_color_balance
AI agents use adjust_color_balance 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.
Color balance adjustments are reversible modifications to image data — they alter the image but can be undone (undo/redo in GIMP). This is Write-category behavior: creates or modifies data reversibly. Severity is medium because misuse could corrupt or deface an image, but the effect is limited to the single image being edited and is fully reversible.
From the tool's definition Tool name 'adjust_color_balance' is one of a suite of image manipulation tools (alongside 'adjust_brightness_contrast', 'adjust_curves', 'adjust_hue_saturation') that modify image data.
Documented attack patterns abuse exactly the kind of access adjust_color_balance 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 adjust_color_balance:
{
"version": "1",
"default": "deny",
"tools": {
"adjust_color_balance": {
"limits": [
{
"counter": "adjust_color_balance_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}adjust_color_balance 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.
adjust_color_balance. 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 adjust_color_balance: 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.
adjust_color_balance 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 adjust_color_balance 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 adjust_color_balance. 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.
adjust_color_balance 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.