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.
This record as markdown: /tools/design-system/get-component-docs.md
What get_component_docs does on Design System
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
component | string | Yes | Component name (e.g., 'button', 'input', 'badge') |
Parameters from the server's own tool schema.
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 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.
Attacks that exploit this kind of access
The rule that runs get_component_docs 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_component_docs, this is the rule to start with:
get_component_docs 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_component_docs call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Design System MCP Server, which means it retrieves data without modifying state.
get_component_docs accepts 1 parameter: component. Required: component. 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_component_docs: 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_component_docs 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_component_docs 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_component_docs. 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_component_docs 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