Get the source code and metadata for a specific shadcn/ui component
AI agents call get_component to retrieve information from shadcn MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns component information without creating, modifying, executing, or deleting anything. It is a straightforward read operation with minimal blast radius — worst case an AI could read publicly available component documentation faster, with no side effects.
From the tool's definition Tool retrieves 'source code and metadata for a specific shadcn/ui component' — pure data fetching with no modification or execution capability. Operates alongside 'get_block', 'list_blocks', and 'list_components', all read-only operations.
Attacks that exploit this kind of access
Get the source code and metadata for a specific shadcn/ui component. It is categorised as a Read tool in the shadcn MCP Server MCP Server, which means it retrieves data without modifying state.
Register the shadcn MCP Server MCP server in PolicyLayer and add a rule for get_component: 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 MCP Server. Nothing to install.
get_component 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 get_component 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 get_component. 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.
get_component is provided by the shadcn MCP Server 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 →