Optimize and clean up Tailwind CSS classes
AI agents use optimize_classes to create or update resources in MCP Tailwind Gemini Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Tailwind Gemini Server environment.
The tool performs class optimization and cleanup, which constitutes modification of configuration or styling data. This is a Write operation because changes are reversible—developers can revert to original classes or re-run the optimization. It does not execute arbitrary code, delete data irreversibly, or trigger external side effects.
From the tool's definition Tool modifies CSS classes by optimizing and cleaning them up. The description explicitly states it performs cleanup operations on Tailwind CSS classes, indicating reversible data modification rather than deletion or execution of arbitrary code.
Documented attack patterns abuse exactly the kind of access optimize_classes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Tailwind Gemini Server, and nothing reaches the server without passing your rules. This is the rule we recommend for optimize_classes:
{
"version": "1",
"default": "deny",
"tools": {
"optimize_classes": {
"limits": [
{
"counter": "optimize_classes_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}optimize_classes 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.
Optimize and clean up Tailwind CSS classes. It is categorised as a Write tool in the MCP Tailwind Gemini Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Tailwind Gemini Server MCP server in PolicyLayer and add a rule for optimize_classes: 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 MCP Tailwind Gemini Server. Nothing to install.
optimize_classes 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 optimize_classes 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 optimize_classes. 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.
optimize_classes is provided by the MCP Tailwind Gemini Server MCP server (tai-dt/mcp-tailwind-gemini). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Tailwind Gemini Server, 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 MCP Tailwind Gemini Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.