AI agents call list_components to retrieve information from Shadcn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
category | string | — | Optional category filter |
Parameters from the server's own tool schema.
This tool queries and returns information about available UI components. It performs a read-only operation that retrieves data without creating, modifying, deleting, or executing anything. The sibling tools (get_block, get_component) reinforce this is a data retrieval service for shadcn/ui documentation/metadata.
From the tool's definition Tool name is 'list_components' and description states 'List all available shadcn/ui components' — this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all available shadcn/ui components. It is categorised as a Read tool in the Shadcn MCP Server, which means it retrieves data without modifying state.
list_components accepts 1 parameter: category. The full parameter table on this page comes from the server's own tool schema.
Register the Shadcn MCP server in PolicyLayer and add a rule for list_components: 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 Shadcn. Nothing to install.
list_components 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 list_components 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 list_components. 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.
list_components is provided by the Shadcn MCP server (@magnusrodseth/shadcn-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 →