Get documentation for public utilities and hooks from @ui5/webcomponents-react-base. Covers Device API, ThemingParameters, useI18nBundle, useViewportRange, and withWebComponent. WHEN TO USE: You need to use device detection, theme-aware CSS variables in JS, internationalization hooks, responsive ...
AI agents call get_public_utils 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 |
|---|---|---|---|
name | string | — | Specific utility/hook name. Omit to see all available utilities. |
Parameters from the server's own tool schema.
This tool retrieves and returns developer documentation and API reference information. It does not create, modify, delete, or execute any code. There are no side effects, state changes, or resource modifications. The 'WHEN TO USE' guidance confirms it is for looking up information (device detection, theming parameters, internationalization hooks, responsive breakpoints).
From the tool's definition Tool description states it 'Get[s] documentation for public utilities and hooks' and 'Returns documentation for one utility per call, or an overview of all 5 utiliti[es]'. This is purely informational retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access get_public_utils 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 get_public_utils:
{
"version": "1",
"default": "deny",
"tools": {
"get_public_utils": {}
}
}get_public_utils 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.
Get documentation for public utilities and hooks from @ui5/webcomponents-react-base. Covers Device API, ThemingParameters, useI18nBundle, useViewportRange, and withWebComponent. WHEN TO USE: You need to use device detection, theme-aware CSS variables in JS, internationalization hooks, responsive breakpoints, or wrap your own custom web components. DO NOT USE FOR: Looking up component props — use get_component_api. For general styling guidance — use get_documentation with section "Knowledge Base > Styling". LIMITS: Returns documentation for one utility per call, or an overview of all 5 utilities. EXAMPLE INPUT: { "name": "ThemingParameters" } EXAMPLE INPUT: { "name": "withWebComponent" } EXAMPLE INPUT: {} (returns overview of all utilities). It is categorised as a Read tool in the Webcomponents React MCP Server, which means it retrieves data without modifying state.
get_public_utils accepts 1 parameter: name. 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 get_public_utils: 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.
get_public_utils 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_public_utils 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_public_utils. 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_public_utils 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.