Delete features by feature IDs or expression filter.
AI agents call delete_features 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.
This tool permanently removes geospatial features from a GIS dataset. Deletion is irreversible and cannot be undone through normal operation—data loss is the direct outcome. While the severity is not critical (the blast radius is typically limited to a single layer or dataset rather than infrastructure-wide), it is destructive because the action cannot be reversed without backups or undo history.
From the tool's definition Tool name is 'delete_features' and description states it will 'Delete features by feature IDs or expression filter.' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete features by feature IDs or expression filter. 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 delete_features: 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.
delete_features 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 delete_features 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 delete_features. 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.
delete_features 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 →