# get_setup_guide

Get setup and installation instructions for integrating the design system into your project

Agent View of the PolicyLayer registry record for `get_setup_guide`. HTML page: https://policylayer.com/tools/design-system/get-setup-guide

## Facts

- Tool: `get_setup_guide`
- 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
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `type` | object | no | Optional: npm for npm/yarn/bun installation, cdn for CDN link. If omitted, returns both options so you can present them to the user. |

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

## Why get_setup_guide is rated Low

This tool retrieves documentation and setup instructions for the design system. It does not modify data, execute arbitrary code, delete anything, or perform financial operations. The only action is reading and returning instructional content to the user. Severity is low because misuse would only result in the user receiving documentation, which poses no security risk.

From the tool's own definition: "Tool is named 'get_setup_guide' and described as retrieving 'setup and installation instructions' - a read-only information retrieval operation with no data modification or execution capability."

## Use case

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

## Other tools on Design System (4)

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