brick_read_me

Returns the building guide, coordinate system, and examples. Call this BEFORE using any other brick tool for the first time.

SERVERBrick Builder MCP App SOURCEdend/brick-mcp-app

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dend-brick-mcp-app/brick-read-me.md

WHAT IT DOES

What brick_read_me does on Brick Builder MCP App

AI agents call brick_read_me to retrieve information from Brick Builder MCP App without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why brick_read_me is rated Low

This tool retrieves and displays instructional content from the server without modifying, executing, or affecting any data or external systems. It is a pure read operation similar to fetching help documentation. The low severity reflects that misuse (e.g., repeatedly calling it) poses minimal risk to the 3D scene or system integrity.

From the tool's definition Tool name 'brick_read_me' and description 'Returns the building guide, coordinate system, and examples' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs brick_read_me 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_read_me, this is the rule to start with:

brick_read_me Allowed

brick_read_me is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "brick_read_me": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Brick Builder MCP App, apply this rule, and every brick_read_me call is checked against it from then on.

FAQ

Questions about brick_read_me

What does the brick_read_me tool do? +

Returns the building guide, coordinate system, and examples. Call this BEFORE using any other brick tool for the first time. It is categorised as a Read tool in the Brick Builder MCP App MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on brick_read_me? +

Register the Brick Builder MCP App MCP server in PolicyLayer and add a rule for brick_read_me: 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_read_me? +

brick_read_me is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit brick_read_me? +

Yes. Add a rate_limit block to the brick_read_me 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_read_me completely? +

Set action: deny in the PolicyLayer policy for brick_read_me. 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_read_me? +

brick_read_me 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.

KEEP EXPLORING

More on Brick Builder MCP App, and thousands of servers like it.

This server

All 9 Brick Builder MCP App tools →

Across the catalogue

claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →