Identify a LEGO minifigure from a text description of its appearance. Describe colors, accessories, theme, or any identifying features and get the best matches from the 18,000+ minifig catalog.
AI agents call identify_minifigure to retrieve information from Brickem without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a search and retrieval operation that queries an existing database of LEGO minifigures and returns matching results. It has no side effects, does not modify any data, and presents minimal security risk even if misused by an AI agent—the worst outcome would be incorrect product recommendations.
From the tool's definition Tool performs identification/lookup from existing catalog: 'Identify a LEGO minifigure from a text description' and 'get the best matches from the 18,000+ minifig catalog'. No data modification, deletion, code execution, or financial transaction occurs.
Attacks that exploit this kind of access
Identify a LEGO minifigure from a text description of its appearance. Describe colors, accessories, theme, or any identifying features and get the best matches from the 18,000+ minifig catalog. It is categorised as a Read tool in the Brickem MCP Server, which means it retrieves data without modifying state.
Register the Brickem MCP server in PolicyLayer and add a rule for identify_minifigure: 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 Brickem. Nothing to install.
identify_minifigure 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 identify_minifigure 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 identify_minifigure. 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.
identify_minifigure is provided by the Brickem MCP server (michiganbricks/brickem-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →