brick_clear_scene
Remove all bricks from the scene.
This record as markdown: /tools/dend-brick-mcp-app/brick-clear-scene.md
What brick_clear_scene does on Brick Builder MCP App
AI agents call brick_clear_scene to permanently remove resources in Brick Builder MCP App, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why brick_clear_scene is rated Critical
This tool meets the Destructive category definition: it irreversibly deletes data (all scene bricks) in a single operation that cannot be undone. While the blast radius is constrained to a single scene within a 3D design application (mitigating to 'high' rather than 'critical'), the operation destroys user work without confirmation or recovery path.
From the tool's definition brick_clear_scene removes all bricks from the scene - a bulk deletion operation that irreversibly wipes out user-created content without granular control or undo capability.
Attacks that exploit this kind of access
The rule that runs brick_clear_scene safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Brick Builder MCP App, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For brick_clear_scene, this is the rule to start with:
brick_clear_scene 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 Brick Builder MCP App, apply this rule, and every brick_clear_scene call is checked against it from then on.
Questions about brick_clear_scene
Remove all bricks from the scene. It is categorised as a Destructive tool in the Brick Builder MCP App MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Brick Builder MCP App MCP server in PolicyLayer and add a rule for brick_clear_scene: 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 Brick Builder MCP App. Nothing to install.
brick_clear_scene 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 brick_clear_scene 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 brick_clear_scene. 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.
brick_clear_scene is provided by the Brick Builder MCP App MCP server (dend/brick-mcp-app). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Brick Builder MCP App, and thousands of servers like it.
Across the catalogue