# brick_set_build_mode

Set the build mode and/or snap flag.

Agent View of the PolicyLayer registry record for `brick_set_build_mode`. HTML page: https://policylayer.com/tools/dend-brick-mcp-app/brick-set-build-mode

## Facts

- Tool: `brick_set_build_mode`
- 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: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

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

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

## Why brick_set_build_mode is rated Medium

This is a Write operation because it creates or modifies data reversibly. Setting build mode and snap flags adjusts how the application behaves during construction, but these settings can be changed again without permanent loss of data or destructive effects. It does not execute arbitrary code, delete content, or cause financial impact.

From the tool's own definition: "The tool name and description indicate it modifies state: 'Set the build mode and/or snap flag.' It changes configuration settings in the 3D scene, which is a reversible modification of the application's operational mode."

## Use case

AI agents use brick_set_build_mode to create or update resources in Brick Builder MCP App, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Brick Builder MCP App environment.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "brick_set_build_mode": {
      "limits": [
        {
          "counter": "brick_set_build_mode_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

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

- `brick_clear_scene` — Destructive — https://policylayer.com/tools/dend-brick-mcp-app/brick-clear-scene.md
- `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

## 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