Browse all 209 available UI5 Web Components for React components across 4 packages with descriptions, categories, and import statements. WHEN TO USE: You need to discover which components exist, find the right component for a use case, or verify a component name before calling get_component_api. ...
AI agents call list_components to retrieve information from Webcomponents React without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
package | string | — | Filter components by npm package name. Omit to show all packages. |
category | string | — | Filter components by category. Omit to show all categories. |
Parameters from the server's own tool schema.
This tool retrieves and queries documentation about available React components—a read-only operation with no side effects. It returns filtered lists of component metadata (names, descriptions, categories, import statements) to help developers discover components. There is no capability to modify, execute, or delete anything.
From the tool's definition Tool description states it 'Browse[s] all 209 available UI5 Web Components' and 'Returns all matching components at once'. The WHEN TO USE section emphasizes discovery and verification: 'find the right component for a use case, or verify a component name'.
Documented attack patterns abuse exactly the kind of access list_components gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Webcomponents React, and nothing reaches the server without passing your rules. This is the rule we recommend for list_components:
{
"version": "1",
"default": "deny",
"tools": {
"list_components": {}
}
}list_components is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Browse all 209 available UI5 Web Components for React components across 4 packages with descriptions, categories, and import statements. WHEN TO USE: You need to discover which components exist, find the right component for a use case, or verify a component name before calling get_component_api. DO NOT USE FOR: Getting detailed props or methods — use get_component_api after finding the component name here. LIMITS: Returns all matching components at once (up to 209). Filter by category or package to reduce output size. EXAMPLE INPUT: { "category": "Inputs" } EXAMPLE INPUT: { "package": "@ui5/webcomponents-react-charts" } EXAMPLE INPUT: {} (returns all components). It is categorised as a Read tool in the Webcomponents React MCP Server, which means it retrieves data without modifying state.
list_components accepts 2 parameters: package, category. The full parameter table on this page comes from the server's own tool schema.
Register the Webcomponents React 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 Webcomponents React. 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 Webcomponents React MCP server (@ui5/webcomponents-react-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Webcomponents React, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Webcomponents React tools catalogued and risk-classified — across an index of 43,000+ MCP servers.