AI agents call get_component 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 |
|---|---|---|---|
componentName | string | Yes | Name of the component (e.g., "button", "card", "input") |
Parameters from the server's own tool schema.
The tool queries and returns existing component information without creating, modifying, deleting, executing code, or triggering external operations. This is a straightforward data retrieval action typical of documentation or library browsing tools. Low severity because exposure carries minimal risk: an AI agent calling this tool repeatedly cannot harm systems or data.
From the tool's definition Tool retrieves 'source code and metadata for a specific shadcn/ui component' — a read-only operation with no side effects or data modifications.
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, which means it retrieves data without modifying state.
get_component accepts 1 parameter: componentName. Required: componentName. 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 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. 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 (@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 →