Delete a saved bookmark.
AI agents call sdk_delete_bookmark to permanently remove resources in UI Bridge MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes a bookmark, which cannot be undone. Although the blast radius is scoped to a single bookmark (not system-critical data), the destructive nature of deletion and lack of recovery options places it in the Destructive category rather than Write.
From the tool's definition The tool name is 'sdk_delete_bookmark' and the description states it will 'Delete a saved bookmark.' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a saved bookmark. It is categorised as a Destructive tool in the UI Bridge MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the UI Bridge MCP server in PolicyLayer and add a rule for sdk_delete_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 UI Bridge MCP. Nothing to install.
sdk_delete_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 sdk_delete_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 sdk_delete_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.
sdk_delete_bookmark is provided by the UI Bridge MCP server (qontinui/ui-bridge-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 →