New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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.

SERVERBrick Builder MCP App SOURCEdend/brick-mcp-app
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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'

Questions about brick_remove_brick

What does the brick_remove_brick tool do? +

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.

How do I enforce a policy on brick_remove_brick? +

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.

What risk level is brick_remove_brick? +

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.

Can I rate-limit brick_remove_brick? +

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.

How do I block brick_remove_brick completely? +

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.

What MCP server provides brick_remove_brick? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Brick Builder MCP App's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.