This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/brickset-search.md
What brickset_search does on UnClick
AI agents call brickset_search to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
year | string | — | |
query | string | — | |
theme | string | — | |
api_key | string | — | |
pageSize | number | — |
Parameters from the server's own tool schema.
Why brickset_search is rated Low
This tool performs a data retrieval operation against a public LEGO set database (Brickset). It has no capability to modify data, execute arbitrary code, move funds, or delete information. The blast radius of misuse is minimal — an agent could only retrieve excessive amounts of LEGO set information, which poses negligible security risk.
From the tool's definition Tool name and description: 'Search LEGO sets via Brickset API' — search is a read-only operation that queries and retrieves data without modifying, executing code, or causing side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs brickset_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For brickset_search, this is the rule to start with:
brickset_search 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 UnClick, apply this rule, and every brickset_search call is checked against it from then on.
Questions about brickset_search
Search LEGO sets via Brickset API. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
brickset_search accepts 5 parameters: year, query, theme, api_key, pageSize. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for brickset_search: 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 UnClick. Nothing to install.
brickset_search 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 brickset_search 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 brickset_search. 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.
brickset_search is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue