Remove a spatial bookmark by its ID.
AI agents call remove_bookmark 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 removes/deletes a spatial bookmark, which is an irreversible deletion operation. However, the blast radius is low since bookmarks are lightweight saved views with no impact on actual GIS data or layers.
From the tool's definition Remove a spatial bookmark by its ID
Attacks that exploit this kind of access
Remove a spatial bookmark by its ID. 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_bookmark: 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_bookmark 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_bookmark 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_bookmark. 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_bookmark 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 →