AI agents use save_image to create or update resources in Inkscape — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Inkscape environment.
This tool creates or modifies files by saving image data, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial). The severity is medium because overwriting files could cause data loss if the agent saves to an incorrect path, but the operation is reversible via undo or file recovery.
From the tool's definition Tool name 'save_image' indicates it writes/persists data to disk. The server context (Inkscape vector graphics editing) confirms this modifies files. Description is empty, slightly reducing confidence.
Documented attack patterns abuse exactly the kind of access save_image gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Inkscape, and nothing reaches the server without passing your rules. This is the rule we recommend for save_image:
{
"version": "1",
"default": "deny",
"tools": {
"save_image": {
"limits": [
{
"counter": "save_image_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_image 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.
save_image. It is categorised as a Write tool in the Inkscape MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Inkscape MCP server in PolicyLayer and add a rule for save_image: 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 Inkscape. Nothing to install.
save_image 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 save_image 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 save_image. 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.
save_image is provided by the Inkscape MCP server (sandraschi/inkscape-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Inkscape, 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.
58 Inkscape tools catalogued and risk-classified — across an index of 43,000+ MCP servers.