# brick_clear_scene

Remove all bricks from the scene.

Agent View of the PolicyLayer registry record for `brick_clear_scene`. HTML page: https://policylayer.com/tools/dend-brick-mcp-app/brick-clear-scene

## Facts

- Tool: `brick_clear_scene`
- Server: Brick Builder MCP App (`dend/brick-mcp-app`) — https://policylayer.com/tools/dend-brick-mcp-app.md
- Homepage: https://github.com/dend/brick-mcp-app
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "brick_clear_scene",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Brick Builder MCP App:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "brick_clear_scene"
  ]
}
```

## Other tools on Brick Builder MCP App (8)

- `brick_remove_brick` — Destructive — https://policylayer.com/tools/dend-brick-mcp-app/brick-remove-brick.md
- `brick_export_scene` — Read — https://policylayer.com/tools/dend-brick-mcp-app/brick-export-scene.md
- `brick_get_available` — Read — https://policylayer.com/tools/dend-brick-mcp-app/brick-get-available.md
- `brick_get_scene` — Read — https://policylayer.com/tools/dend-brick-mcp-app/brick-get-scene.md
- `brick_read_me` — Read — https://policylayer.com/tools/dend-brick-mcp-app/brick-read-me.md
- `brick_search_parts` — Read — https://policylayer.com/tools/dend-brick-mcp-app/brick-search-parts.md
- `brick_place` — Write — https://policylayer.com/tools/dend-brick-mcp-app/brick-place.md
- `brick_set_build_mode` — Write — https://policylayer.com/tools/dend-brick-mcp-app/brick-set-build-mode.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dend-brick-mcp-app · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dend-brick-mcp-app