Retrieve UI5 Web Components for React documentation, guides, and knowledge base articles. Documentation is bundled locally for instant offline access. WHEN TO USE: You need guidance on how to use the library — setup, styling, event handling, SSR, slots, i18n. DO NOT USE FOR: Looking up specific c...
AI agents call get_documentation 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 |
|---|---|---|---|
query | string | — | Free-form search query to find relevant documentation. Searches across section names, descriptions, tags, and content topics. Examples: "styling", "migration", |
endLine | integer | — | End line number (1-based, inclusive) for reading a portion of the documentation. Requires fetchContent: true. If omitted with startLine, reads to end of file. |
section | string | — | Specific documentation section to retrieve by exact name. Use this for direct access when you know which section you need. Examples: "Getting Started", "Migrati |
startLine | integer | — | Start line number (1-based, inclusive) for reading a portion of the documentation. Requires fetchContent: true. Useful for large documents like the Change Log o |
fetchContent | boolean | — | Whether to include the full documentation markdown content. Set to true to retrieve full documentation text in addition to metadata. Content is read from bundle |
Parameters from the server's own tool schema.
This tool retrieves and searches documentation content. It has no capability to modify, delete, execute code, or perform any irreversible actions. The 'WHEN TO USE' section confirms it is purely informational guidance. The only operations mentioned are reading and searching, making this clearly a Read category tool with low severity risk—an AI agent cannot cause harm by requesting documentation.
From the tool's definition Tool description states: 'Retrieve UI5 Web Components for React documentation' and 'Documentation is bundled locally for instant offline access.' The workflow specifies 'Call without parameters to see all available sections' and 'Use section parameter for…
Risk signalsAccepts freeform code/query input (query)
Documented attack patterns abuse exactly the kind of access get_documentation 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_documentation:
{
"version": "1",
"default": "deny",
"tools": {
"get_documentation": {}
}
}get_documentation 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.
Retrieve UI5 Web Components for React documentation, guides, and knowledge base articles. Documentation is bundled locally for instant offline access. WHEN TO USE: You need guidance on how to use the library — setup, styling, event handling, SSR, slots, i18n. DO NOT USE FOR: Looking up specific component props or methods — use get_component_api instead. For public utilities/hooks from @ui5/webcomponents-react-base — use get_public_utils. WORKFLOW: Call without parameters to see all available sections. Use section parameter for direct access, query for search. LIMITS: When fetchContent is true, full content is returned for at most 3 matching sections to control output size. EXAMPLE INPUT: { "section": "Knowledge Base > Styling", "fetchContent": true } EXAMPLE INPUT: { "query": "i18n", "fetchContent": true } EXAMPLE INPUT: {} (returns catalog of all documentation sections). It is categorised as a Read tool in the Webcomponents React MCP Server, which means it retrieves data without modifying state.
get_documentation accepts 5 parameters: query, endLine, section, startLine, fetchContent. 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_documentation: 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_documentation 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_documentation 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_documentation. 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_documentation 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.