AI agents use merge_layers 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.
Merging layers in Inkscape modifies the document by combining layer structures, but this operation can be undone (Ctrl+Z in Inkscape). It is not destructive data deletion, nor does it execute arbitrary code or trigger financial transactions. The tool fits Write rather than Execute because it performs a specific, predictable transformation of graphics data rather than running arbitrary commands.
From the tool's definition Tool name is 'merge_layers' on an Inkscape vector graphics editing server. Merging layers modifies the document structure by combining layers into one, which is a reversible operation typical of Write category tools.
Documented attack patterns abuse exactly the kind of access merge_layers 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 merge_layers:
{
"version": "1",
"default": "deny",
"tools": {
"merge_layers": {
"limits": [
{
"counter": "merge_layers_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}merge_layers 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.
merge_layers. 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 merge_layers: 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.
merge_layers 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 merge_layers 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 merge_layers. 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.
merge_layers 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.