brickset_get_set
Get a specific LEGO set from Brickset by set number.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/brickset-get-set.md
What brickset_get_set does on UnClick
AI agents call brickset_get_set 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 |
|---|---|---|---|
api_key | string | — | |
setNumber | string | Yes |
Parameters from the server's own tool schema.
Why brickset_get_set is rated Low
This tool retrieves data about a LEGO set from an external database (Brickset) based on a set number parameter. It performs a simple lookup with no ability to modify, delete, or execute operations. The blast radius of misuse is minimal—an agent could only retrieve unwanted information about LEGO sets, which poses no security, financial, or destructive risk.
From the tool's definition Tool name 'brickset_get_set' and description 'Get a specific LEGO set from Brickset by set number' indicate a retrieval operation with no modification or execution capability.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs brickset_get_set 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_get_set, this is the rule to start with:
brickset_get_set 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_get_set call is checked against it from then on.
Questions about brickset_get_set
Get a specific LEGO set from Brickset by set number. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
brickset_get_set accepts 2 parameters: api_key, setNumber. Required: setNumber. 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_get_set: 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_get_set 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_get_set 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_get_set. 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_get_set 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