# get_css_tokens

Get all CSS custom property tokens (--color-*, --space-*, etc.) for a specific category. Use these instead of hardcoded values.

Agent View of the PolicyLayer registry record for `get_css_tokens`. HTML page: https://policylayer.com/tools/design-system/get-css-tokens

## Facts

- Tool: `get_css_tokens`
- Server: Design System (`@triptease/design-system-mcp`) — https://policylayer.com/tools/design-system.md
- Install: `npx -y @triptease/design-system-mcp`
- Homepage: https://www.npmjs.com/package/@triptease/design-system-mcp
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| 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.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_css_tokens",
    "arguments": {
      "category": "<category>"
    }
  }
}
```

## 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 own definition: "Tool description states 'Get all CSS custom property tokens' — this is a retrieval operation that queries design system documentation without modifying any data."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Design System:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_css_tokens": {}
  }
}
```

## Other tools on Design System (4)

- `get_component_docs` — Read — https://policylayer.com/tools/design-system/get-component-docs.md
- `get_setup_guide` — Read — https://policylayer.com/tools/design-system/get-setup-guide.md
- `list_components` — Read — https://policylayer.com/tools/design-system/list-components.md
- `list_css_tokens` — Read — https://policylayer.com/tools/design-system/list-css-tokens.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=design-system · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/design-system