Apply a TweakCN theme preset to the project
AI agents use apply_theme to create or update resources in Shadcn Ui — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Shadcn Ui environment.
The tool writes/modifies project theme configuration. While reversible (themes can be changed or reverted), it alters project state and could affect the appearance or behavior of UI components across the application. This is Write rather than Execute because it applies a predefined preset rather than executing arbitrary code, and it's not destructive since the previous theme state could be recovered.
From the tool's definition Tool name 'apply_theme' and description 'Apply a TweakCN theme preset to the project' indicate the tool modifies project configuration/styling by applying a theme. This creates or modifies project state (theme settings) reversibly.
Documented attack patterns abuse exactly the kind of access apply_theme 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 apply_theme:
{
"version": "1",
"default": "deny",
"tools": {
"apply_theme": {
"limits": [
{
"counter": "apply_theme_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}apply_theme 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.
Free to start. No card required.
Apply a TweakCN theme preset to the project. It is categorised as a Write tool in the Shadcn Ui MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Shadcn Ui MCP server in PolicyLayer and add a rule for apply_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 Shadcn Ui. Nothing to install.
apply_theme 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 apply_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 apply_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.
apply_theme 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.