# get_component_docs

Get full documentation for a Triptease design system component including attributes, events, slots, CSS custom properties, and usage examples. Use the key from list_components.

Agent View of the PolicyLayer registry record for `get_component_docs`. HTML page: https://policylayer.com/tools/design-system/get-component-docs

## Facts

- Tool: `get_component_docs`
- 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 |
| --- | --- | --- | --- |
| `component` | string | yes | Component name (e.g., 'button', 'input', 'badge') |

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_component_docs",
    "arguments": {
      "component": "<component>"
    }
  }
}
```

## Why get_component_docs is rated Low

This tool queries and retrieves documentation about design system components. It has no side effects, cannot modify data, cannot execute code, and cannot delete information. It is purely informational, making it a Read operation with low severity risk.

From the tool's own definition: "Tool description states 'Get full documentation' and retrieves design system component information. The verb 'Get' and the read-only nature of documentation retrieval indicates no data modification, deletion, or code execution."

## Use case

AI agents call get_component_docs 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_component_docs": {}
  }
}
```

## Other tools on Design System (4)

- `get_css_tokens` — Read — https://policylayer.com/tools/design-system/get-css-tokens.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