shadcn_theme
Return a brand-themed @theme inline CSS block for shadcn/ui + Tailwind v4. Defaults to the 0n brand theme (dark, accent #6EE05A green-teal-purple gradient). Drop into globals.css directly after @import
This record as markdown: /tools/io-github-0nork-0nmcp/shadcn-theme.md
What shadcn_theme does on 0nmcp
AI agents call shadcn_theme to permanently remove resources in 0nmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why shadcn_theme is rated Critical
An AI agent that decides to call shadcn_theme doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from 0nmcp is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs shadcn_theme 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_theme, this is the rule to start with:
shadcn_theme is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect 0nmcp, apply this rule, and every shadcn_theme call is checked against it from then on.
Questions about shadcn_theme
Return a brand-themed @theme inline CSS block for shadcn/ui + Tailwind v4. Defaults to the 0n brand theme (dark, accent #6EE05A green-teal-purple gradient). Drop into globals.css directly after @import. It is categorised as a Destructive tool in the 0nmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 0n MCP server in PolicyLayer and add a rule for shadcn_theme: 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_theme is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the shadcn_theme 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_theme. 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_theme 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.
Across the catalogue