brick_remove_brick
Remove a single brick by its ID. Use brick_get_scene to find brick IDs. Also removes any bricks that lose support as a result.
This record as markdown: /tools/dend-brick-mcp-app/brick-remove-brick.md
What brick_remove_brick does on Brick Builder MCP App
AI agents call brick_remove_brick 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_remove_brick is rated Critical
This tool irreversibly removes a brick and potentially cascades to remove additional bricks that lose structural support. There is no indication of an undo mechanism, making this a destructive operation. The cascade effect amplifies the blast radius beyond a single element.
From the tool's definition 'Remove a single brick by its ID' and 'Also removes any bricks that lose support as a result'
Attacks that exploit this kind of access
The rule that runs brick_remove_brick 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_remove_brick, this is the rule to start with:
brick_remove_brick 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_remove_brick call is checked against it from then on.
Questions about brick_remove_brick
Remove a single brick by its ID. Use brick_get_scene to find brick IDs. Also removes any bricks that lose support as a result. 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_remove_brick: 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_remove_brick 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_remove_brick 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_remove_brick. 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_remove_brick 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