Remove a layer from the project by its layer ID. This is irreversible.
AI agents call remove_layer to permanently remove resources in QGIS MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool irreversibly removes data (a layer) from a GIS project. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While the underlying layer file may still exist on disk, the project state is permanently altered and the operation cannot be undone within the project context.
From the tool's definition 'Remove a layer from the project by its layer ID. This is irreversible.' - the description explicitly states the action is irreversible, and removing a layer from a GIS project permanently deletes its reference and associated work.
Attacks that exploit this kind of access
Remove a layer from the project by its layer ID. This is irreversible. It is categorised as a Destructive tool in the QGIS MCP 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 QGIS MCP. 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 (nkarasiak/qgis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →