brick_search_parts
Search or browse the full LDraw parts library. Without arguments, returns all categories with part counts. Use
This record as markdown: /tools/dend-brick-mcp-app/brick-search-parts.md
What brick_search_parts does on Brick Builder MCP App
AI agents call brick_search_parts 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_search_parts is rated Low
This tool retrieves information from a static parts library and returns catalog data. It performs no mutations, deletions, code execution, or financial operations. Searching and browsing are read-only operations with no destructive or side-effect capabilities. The blast radius if misused is minimal—an AI agent could retrieve catalog data but cannot modify scenes, delete content, or trigger external operations.
From the tool's definition Tool name 'brick_search_parts' and description 'Search or browse the full LDraw parts library' indicate querying/browsing a catalog.
Attacks that exploit this kind of access
The rule that runs brick_search_parts 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_search_parts, this is the rule to start with:
brick_search_parts 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_search_parts call is checked against it from then on.
Questions about brick_search_parts
Search or browse the full LDraw parts library. Without arguments, returns all categories with part counts. Use. 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_search_parts: 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_search_parts 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_search_parts 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_search_parts. 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_search_parts 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