get_css_tokens
Get all CSS custom property tokens (--color-*, --space-*, etc.) for a specific category. Use these instead of hardcoded values.
This record as markdown: /tools/design-system/get-css-tokens.md
What get_css_tokens does on Design System
AI agents call get_css_tokens to retrieve information from Design System without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
category | string | Yes | Token category: one of the category names returned by the listCSSTokens tool. |
Parameters from the server's own tool schema.
Why get_css_tokens is rated Low
This tool retrieves CSS token metadata from a design system documentation server. It has no capability to modify, delete, or execute anything — it only returns reference data for frontend styling. The blast radius of misuse is minimal; an AI could at worst retrieve tokens it shouldn't see, but cannot alter the design system or trigger external actions.
From the tool's definition Tool description states 'Get all CSS custom property tokens' — this is a retrieval operation that queries design system documentation without modifying any data.
Attacks that exploit this kind of access
The rule that runs get_css_tokens safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Design System, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_css_tokens, this is the rule to start with:
get_css_tokens is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Design System, apply this rule, and every get_css_tokens call is checked against it from then on.
Questions about get_css_tokens
Get all CSS custom property tokens (--color-*, --space-*, etc.) for a specific category. Use these instead of hardcoded values. It is categorised as a Read tool in the Design System MCP Server, which means it retrieves data without modifying state.
get_css_tokens accepts 1 parameter: category. Required: category. The full parameter table on this page comes from the server's own tool schema.
Register the Design System MCP server in PolicyLayer and add a rule for get_css_tokens: 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 Design System. Nothing to install.
get_css_tokens is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_css_tokens 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 get_css_tokens. 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.
get_css_tokens is provided by the Design System MCP server (@triptease/design-system-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Design System, and thousands of servers like it.
This server
Across the catalogue