delete_camera_bookmark
Delete one session-scoped camera bookmark and its comparison baselines. Returns deleted=false when already absent. Use list_camera_bookmarks to inspect remaining names.
This record as markdown: /tools/sbox/delete-camera-bookmark.md
What delete_camera_bookmark does on Sbox
AI agents call delete_camera_bookmark to permanently remove resources in Sbox, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_camera_bookmark is rated Critical
Irreversibly removes bookmarks and associated baselines; cannot be undone without manual recreation.
From the tool's definition Delete one session-scoped camera bookmark and its comparison baselines.
Attacks that exploit this kind of access
The rule that runs delete_camera_bookmark safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sbox, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_camera_bookmark, this is the rule to start with:
delete_camera_bookmark is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Sbox, apply this rule, and every delete_camera_bookmark call is checked against it from then on.
Questions about delete_camera_bookmark
Delete one session-scoped camera bookmark and its comparison baselines. Returns deleted=false when already absent. Use list_camera_bookmarks to inspect remaining names. It is categorised as a Destructive tool in the Sbox MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sbox MCP server in PolicyLayer and add a rule for delete_camera_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 Sbox. Nothing to install.
delete_camera_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 delete_camera_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 delete_camera_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.
delete_camera_bookmark is provided by the Sbox MCP server (sbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sbox, and thousands of servers like it.
Across the catalogue