brickset_search

Search LEGO sets via Brickset API.

Server UnClick @unclick/mcp-server
Category Read
Risk class Low
Parameters 50 required

What brickset_search does on UnClick

AI agents call brickset_search to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
year string
query string
theme string
api_key string
pageSize number

Parameters from the server's own tool schema.

Why brickset_search needs a policy

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 signalsAccepts freeform code/query input (query) · Handles credentials or secrets (api_key)

Questions about brickset_search

What does the brickset_search tool do? +

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.

What parameters does brickset_search accept? +

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.

How do I enforce a policy on brickset_search? +

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.

What risk level is brickset_search? +

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

Can I rate-limit brickset_search? +

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.

How do I block brickset_search completely? +

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.

What MCP server provides brickset_search? +

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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.