brick_get_available
Returns popular brick types with their IDs and dimensions. You can also use any LDraw part number not listed here. For the full library (15,000+ parts), use brick_search_parts to search or browse by category. Call this to learn what bricks you can use before building.
This record as markdown: /tools/dend-brick-mcp-app/brick-get-available.md
What brick_get_available does on Brick Builder MCP App
AI agents call brick_get_available 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.
Why brick_get_available is rated Low
This tool simply queries and returns metadata about available brick types and their properties (IDs, dimensions). It is a pure read operation with no capability to modify state, execute code, or trigger external effects. The low severity reflects that misuse cannot cause material harm—at worst, an agent would request information about available bricks.
From the tool's definition Tool name 'brick_get_available' and description 'Returns popular brick types' indicates data retrieval with no side effects. No modification, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
The rule that runs brick_get_available 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_get_available, this is the rule to start with:
brick_get_available is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Brick Builder MCP App, apply this rule, and every brick_get_available call is checked against it from then on.
Questions about brick_get_available
Returns popular brick types with their IDs and dimensions. You can also use any LDraw part number not listed here. For the full library (15,000+ parts), use brick_search_parts to search or browse by category. Call this to learn what bricks you can use before building. It is categorised as a Read tool in the Brick Builder MCP App MCP Server, which means it retrieves data without modifying state.
Register the Brick Builder MCP App MCP server in PolicyLayer and add a rule for brick_get_available: 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.
brick_get_available is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the brick_get_available 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.
Set action: deny in the PolicyLayer policy for brick_get_available. 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.
brick_get_available 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.
This server
Across the catalogue