AI agents call lego_set_parts 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | — | |
set_num | string | Yes |
Parameters from the server's own tool schema.
The tool fetches a list of parts for a given LEGO set. This is a read-only query against what appears to be a LEGO parts database (likely Rebrickable or similar). No data is created, modified, or deleted. Blast radius if misused is minimal — at most, an agent wastes API quota.
From the tool's definition 'Get the parts list for a LEGO set' — purely a data retrieval operation with no side effects
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
Get the parts list for a LEGO set. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
lego_set_parts accepts 2 parameters: api_key, set_num. Required: set_num. 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 lego_set_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 UnClick. Nothing to install.
lego_set_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 lego_set_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 lego_set_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.
lego_set_parts 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.
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 →