Repository navigation
Configuration Bricklayer Json
The .bricklayer.json file controls per-project tool behavior and security settings.
Two commands produce and maintain this file — you should rarely need to edit it by hand:
| Command | Purpose |
|---|---|
bricklayer init |
Generate a fresh file with deploy-mode-aware defaults (also runs during bricklayer install) |
bricklayer config:set |
Update a single value with validation, round-trip verification, and an interactive picker for discoverability |
The interactive config:set flow lists every runtime-configurable tool with its current state, lets you drill into a specific setting, and prompts for the new value with type-aware validation. See CLI Commands → config:set.
Configuration is loaded in priority order (highest wins):
-
Environment variables — Override any setting via
BRICKLAYER_*(see Environment Variables) -
Project config —
.bricklayer.jsonin project root - Built-in defaults — Safe defaults for all tools
A generated developer-mode file contains one entry per runtime-configurable tool (35 entries total). Destructive tools default to enabled: false, everything else defaults to enabled: true:
{
"tools": {
"code-runner": {
"enabled": true,
"allow_write": false,
"max_timeout": 60
},
"database-query": {
"enabled": true,
"max_rows": 100
},
"log": {
"enabled": true,
"max_lines": 500
},
"diagnose-performance": { "enabled": true },
"product-create": { "enabled": true },
"product-update": { "enabled": true },
"product-delete": { "enabled": false },
"category-create": { "enabled": true },
"category-delete": { "enabled": false },
"order-cancel": { "enabled": false },
"customer-delete": { "enabled": false },
"generate-module": { "enabled": false }
}
}Every key in a generated file maps to a requireToolEnabled() call site in the source code — so the file never contains dead keys, and new configurable tools are picked up automatically by bricklayer init via a one-time source scan.
Each tool supports an enabled boolean and tool-specific options:
| Key | Type | Default | Description |
|---|---|---|---|
enabled |
bool | true (dev) / false (prod) | Enable code execution |
allow_write |
bool | false | Allow write operations (false = changes rolled back) |
max_timeout |
int | 60 | Max execution time in seconds |
| Key | Type | Default | Description |
|---|---|---|---|
enabled |
bool | true | Enable SQL queries |
max_rows |
int | 100 (dev) / 50 (prod) | Maximum rows returned per query |
| Key | Type | Default | Description |
|---|---|---|---|
enabled |
bool | true | Enable log reading |
max_lines |
int | 500 | Maximum log lines returned per read |
| Key | Type | Default | Description |
|---|---|---|---|
enabled |
bool | true | Enable performance diagnostics |
These tools are disabled by default in both developer and production modes. They must be explicitly enabled (enabled: true) to run:
| Tool | Type |
|---|---|
product-delete |
Catalog |
category-delete |
Catalog |
customer-delete |
Customer |
customer-address-delete |
Customer |
order-cancel |
Order |
order-create |
Order |
creditmemo-create |
Order |
Disabled by default in both developer and production modes:
| Tool |
|---|
generate-module |
generate-model |
generate-controller |
generate-api |
To enable any of these temporarily, run:
vendor/bin/bricklayer config:set tools.generate-module.enabled trueControl which development guidelines are loaded:
{
"guidelines": {
"include": ["core", "modules", "patterns", "database"],
"exclude": ["ecosystem/adobe-commerce"]
}
}Specify which agents to generate configuration files for:
{
"agents": ["claude-code", "cursor", "copilot", "jetbrains", "gemini"]
}The MCP server monitors .bricklayer.json mtime. Changes are picked up automatically on the next tool call without requiring a server restart. This applies to both hand-edits and config:set updates.
After a successful config:set the command prints a reminder:
! [NOTE] Changes apply on the next MCP tool call — bricklayer hot-reloads
! .bricklayer.json automatically based on file mtime, so no agent
! restart is required. If a tool call is already in flight, it will
! finish with the old config; subsequent calls will see the new value.
| Setting | Developer | Production |
|---|---|---|
code-runner |
enabled (read-only) | disabled |
database-query.max_rows |
100 | 50 |
| Destructive tools | disabled | disabled |
| Code generation | disabled | disabled |
| Total disabled tool count | 10 | 11 (adds code-runner) |
- Environment Variables — Override settings via env vars
- Security — Production safety system
Getting Started
Architecture
Tools Reference
- Overview (84 Tools)
- Introspection
- Catalog
- Orders
- Customers
- Database
- Logs & Diagnostics
- GraphQL
- Development
Configuration
Guidelines & Skills
Code Generation
Diagnostics
Security