AI agents call lego_themes 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 | — |
Parameters from the server's own tool schema.
This tool performs a read-only operation to list/fetch LEGO theme data from an external API (Rebrickable). There is no data creation, modification, deletion, code execution, or financial impact. The blast radius of misuse is minimal—an agent could only retrieve publicly available LEGO theme information.
From the tool's definition Tool name 'lego_themes' and description 'List all LEGO themes from Rebrickable' indicate a query operation that retrieves data without modification or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
List all LEGO themes from Rebrickable. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
lego_themes accepts 1 parameter: api_key. 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_themes: 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_themes 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_themes 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_themes. 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_themes 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 →