Critical Risk →

delete_layer

delete_layer

How to control delete_layer ↓

What delete_layer does on Inkscape

AI agents call delete_layer to permanently remove resources in Inkscape — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_layer needs a policy

Deleting a layer cannot be undone by standard undo mechanisms if the operation is committed (depending on Inkscape state), and it results in permanent loss of all vector graphics and data contained within that layer. This is a destructive operation with significant blast radius in an AI-controlled graphics editing context.

From the tool's definition Tool name is 'delete_layer' which explicitly indicates irreversible deletion of a layer from the Inkscape document.

Documented attack patterns abuse exactly the kind of access delete_layer gives an agent:

How to control delete_layer

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 delete_layer:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_layer"
  ]
}

delete_layer disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Inkscape — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_layer

What does the delete_layer tool do? +

delete_layer. It is categorised as a Destructive tool in the Inkscape MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_layer? +

Register the Inkscape MCP server in PolicyLayer and add a rule for delete_layer: 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.

What risk level is delete_layer? +

delete_layer is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_layer? +

Yes. Add a rate_limit block to the delete_layer 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.

How do I block delete_layer completely? +

Set action: deny in the PolicyLayer policy for delete_layer. 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.

What MCP server provides delete_layer? +

delete_layer 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.

Enforce policy on every Inkscape tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.