AI agents call remove_layer to permanently remove resources in QGISMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a layer from a GIS project is a destructive action: the layer (including its symbology, configuration, and association with the project) is permanently removed. While the underlying data file may still exist on disk, the layer definition, styling, and project-level metadata are lost and cannot be trivially recovered. This qualifies as Destructive rather than Write, as the action is not easily reversible.
From the tool's definition 'Remove a layer from the project by its ID' — removing a layer is irreversible within the current project state and destroys the layer's presence and configuration in the project.
Documented attack patterns abuse exactly the kind of access remove_layer gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and QGISMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_layer:
{
"version": "1",
"default": "deny",
"hide": [
"remove_layer"
]
}remove_layer disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a layer from the project by its ID. It is categorised as a Destructive tool in the QGISMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the QGIS MCP server in PolicyLayer and add a rule for remove_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 QGISMCP. Nothing to install.
remove_layer is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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.
Set action: deny in the PolicyLayer policy for remove_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.
remove_layer is provided by the QGIS MCP server (kicker315/deepseek_qgis_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from QGISMCP, 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.
17 QGISMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.