AI agents use apply_drop_shadow 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.
The tool modifies image data by adding a drop shadow effect—a reversible transformation. This qualifies as Write (creates or modifies data reversibly) rather than Execute, because the operation is a specific visual filter with deterministic behavior, not arbitrary code execution. Severity is medium because misuse could deface or obscure images, but the effect is non-destructive and easily undone.
From the tool's definition Tool name 'apply_drop_shadow' indicates it applies a visual effect to an image; sibling tools like 'apply_gaussian_blur', 'apply_vignette', 'apply_emboss', and 'apply_noise' all modify image content reversibly. GIMP context confirms this is image manipulation.
Documented attack patterns abuse exactly the kind of access apply_drop_shadow 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 apply_drop_shadow:
{
"version": "1",
"default": "deny",
"tools": {
"apply_drop_shadow": {
"limits": [
{
"counter": "apply_drop_shadow_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}apply_drop_shadow 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.
apply_drop_shadow. 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 apply_drop_shadow: 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.
apply_drop_shadow 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 apply_drop_shadow 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 apply_drop_shadow. 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.
apply_drop_shadow 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.