shadcn_install_command
Generate the exact shell command to install a shadcn component. Supports npm, pnpm, yarn, and bun. Pass multiple components to install in one call.
This record as markdown: /tools/io-github-0nork-0nmcp/shadcn-install-command.md
What shadcn_install_command does on 0nmcp
AI agents use shadcn_install_command to create or update resources in 0nmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 0nmcp environment.
Why shadcn_install_command is rated Medium
An AI agent can call shadcn_install_command faster than any human can review: one bad instruction and it creates or modifies resources in 0nmcp by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs shadcn_install_command safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For shadcn_install_command, this is the rule to start with:
shadcn_install_command stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 0nmcp, apply this rule, and every shadcn_install_command call is checked against it from then on.
Questions about shadcn_install_command
Generate the exact shell command to install a shadcn component. Supports npm, pnpm, yarn, and bun. Pass multiple components to install in one call. It is categorised as a Write tool in the 0nmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 0n MCP server in PolicyLayer and add a rule for shadcn_install_command: 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 0nmcp. Nothing to install.
shadcn_install_command is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the shadcn_install_command 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 shadcn_install_command. 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.
shadcn_install_command is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0n, and thousands of servers like it.
This server
Across the catalogue