AI agents use fill to create or update resources in 🪄 ImageSorcery MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 🪄 ImageSorcery MCP environment.
Image fill operations modify pixel data reversibly (images can be re-edited or reverted from source), making this a Write rather than Destructive action. Severity is medium because misuse could alter important images, but effects are not irreversible if originals are preserved. Confidence is 0.7 due to empty description—higher confidence would require explicit documentation.
From the tool's definition Tool named 'fill' on an image manipulation server (ImageSorcery MCP) with sibling tools like blur, crop, draw_arrows, etc. The name 'fill' typically means filling regions with color or patterns, modifying image data. Description is empty, reducing confidence.
Documented attack patterns abuse exactly the kind of access fill gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and 🪄 ImageSorcery MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for fill:
{
"version": "1",
"default": "deny",
"tools": {
"fill": {
"limits": [
{
"counter": "fill_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}fill 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.
fill. It is categorised as a Write tool in the 🪄 ImageSorcery MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 🪄 ImageSorcery MCP server in PolicyLayer and add a rule for fill: 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 🪄 ImageSorcery MCP. Nothing to install.
fill 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 fill 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 fill. 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.
fill is provided by the 🪄 ImageSorcery MCP server (sunriseapps/imagesorcery-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 🪄 ImageSorcery MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
17 🪄 ImageSorcery MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.