Convert traditional CSS to TailwindCSS utility classes
AI agents use convert_css_to_tailwind to create or update resources in Tailwindcss — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tailwindcss environment.
An AI agent can call convert_css_to_tailwind faster than any human can review — one bad instruction and it creates or modifies resources in Tailwindcss by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Convert traditional CSS to TailwindCSS utility classes. It is categorised as a Write tool in the Tailwindcss MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tailwindcss MCP server in PolicyLayer and add a rule for convert_css_to_tailwind: 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 Tailwindcss. Nothing to install.
convert_css_to_tailwind 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 convert_css_to_tailwind 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 convert_css_to_tailwind. 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.
convert_css_to_tailwind is provided by the Tailwindcss MCP server (tailwindcss-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.