Deletes current selection
AI agents call selection_delete to permanently remove resources in Open Brush MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible delete operation on selected content within Open Brush. While the blast radius is limited to the current painting session (data may be recoverable via undo or backup), the action cannot be undone through the tool itself and represents permanent data loss within that context. This qualifies as Destructive rather than Write (which would be reversible modification).
From the tool's definition Tool name 'selection_delete' and description 'Deletes current selection' indicate irreversible removal of data from the 3D painting canvas.
Attacks that exploit this kind of access
Deletes current selection. It is categorised as a Destructive tool in the Open Brush MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Open Brush MCP Server MCP server in PolicyLayer and add a rule for selection_delete: 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 Open Brush MCP Server. Nothing to install.
selection_delete 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 selection_delete 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 selection_delete. 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.
selection_delete is provided by the Open Brush MCP Server MCP server (moz411/openbrush-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 →