Get source code for a specific shadcn/ui v4 block (e.g., calendar-01, dashboard-01)
AI agents call get_block 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 queries and returns source code documentation for UI components. It has no side effects, cannot execute code, and only retrieves existing data. The blast radius of misuse is minimal — an agent might retrieve irrelevant or excessive documentation, but cannot harm systems or data. This is a straightforward Read category tool.
From the tool's definition Tool description states 'Get source code for a specific shadcn/ui v4 block' — the verb 'Get' indicates a retrieval operation. The tool retrieves pre-existing component source code without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access get_block 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_block:
{
"version": "1",
"default": "deny",
"tools": {
"get_block": {}
}
}get_block 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 source code for a specific shadcn/ui v4 block (e.g., calendar-01, dashboard-01). 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_block: 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_block 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_block 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_block. 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_block 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.