Get the source code for a specific shadcn/ui v4 component
AI agents call get_component to retrieve information from Shadcn Ui without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves source code for UI components without modifying, executing, or deleting any data. It is a pure query/fetch operation that provides documentation context about shadcn/ui components. There are no side effects, code execution, or irreversible actions. The blast radius of misuse is minimal—returning the wrong component code would only affect developer context, not system state.
From the tool's definition Tool name and description indicate retrieval only: 'Get the source code for a specific shadcn/ui v4 component'. The verb 'Get' and the read-only operation of retrieving component source code without modification confirm this is a read operation.
Documented attack patterns abuse exactly the kind of access get_component gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Shadcn Ui, and nothing reaches the server without passing your rules. This is the rule we recommend for get_component:
{
"version": "1",
"default": "deny",
"tools": {
"get_component": {}
}
}get_component is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the source code for a specific shadcn/ui v4 component. It is categorised as a Read tool in the Shadcn Ui MCP Server, which means it retrieves data without modifying state.
Register the Shadcn Ui 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 Ui. 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 Ui MCP server (jpisnice/shadcn-ui-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Shadcn Ui, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Shadcn Ui tools catalogued and risk-classified — across an index of 43,000+ MCP servers.