list_components
List all available Triptease design system components with their element names and descriptions. Call this first to discover component keys for get_component_docs.
This record as markdown: /tools/design-system/list-components.md
What list_components does on Design System
AI agents call list_components 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.
Why list_components is rated Low
This tool performs a query operation that returns metadata about available design system components. It produces no modifications, deletions, or state changes. The API is read-only and returns documentation/reference information, making it the lowest-risk category. Blast radius of misuse is minimal—an agent could only enumerate available components, which is non-sensitive reference data.
From the tool's definition Tool name 'list_components' and description 'List all available Triptease design system components' indicates a retrieval/enumeration operation with no side effects. Supports discovery for other Read operations (get_component_docs).
Attacks that exploit this kind of access
The rule that runs list_components 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 list_components, this is the rule to start with:
list_components 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 list_components call is checked against it from then on.
Questions about list_components
List all available Triptease design system components with their element names and descriptions. Call this first to discover component keys for get_component_docs. It is categorised as a Read tool in the Design System MCP Server, which means it retrieves data without modifying state.
Register the Design System MCP server in PolicyLayer and add a rule for list_components: 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.
list_components 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 list_components 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 list_components. 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.
list_components 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