Get scaffolding instructions for a new UI5 Web Components for React application from an official template. WHEN TO USE: The user wants to create a new app, project, or starter using UI5 Web Components for React. WORKFLOW: Call this tool to get the template setup instructions, then execute them. A...
AI agents call create_app 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 |
|---|---|---|---|
appName | string | Yes | Name for the new application directory |
template | string | Yes | Template to use. Available: nextjs-app, nextjs-pages, vite-ts |
Parameters from the server's own tool schema.
The tool retrieves scaffolding/setup instructions rather than executing them. The description explicitly states it returns instructions ('Call this tool to get the template setup instructions, then execute them'), meaning actual execution is a separate step. No files are created, no commands are run — it is purely informational/documentation retrieval.
From the tool's definition Get scaffolding instructions for a new UI5 Web Components for React application from an official template
Risk signalsAccepts raw HTML/template content (template)
Documented attack patterns abuse exactly the kind of access create_app 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 create_app:
{
"version": "1",
"default": "deny",
"tools": {
"create_app": {}
}
}create_app 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 scaffolding instructions for a new UI5 Web Components for React application from an official template. WHEN TO USE: The user wants to create a new app, project, or starter using UI5 Web Components for React. WORKFLOW: Call this tool to get the template setup instructions, then execute them. Available templates: - nextjs-app — Next.js (App Router) - nextjs-pages — Next.js (Pages Router) - vite-ts — Vite.js EXAMPLE INPUT: { "template": "vite-ts", "appName": "my-app" } EXAMPLE INPUT: { "template": "nextjs-app", "appName": "my-dashboard" }. It is categorised as a Read tool in the Webcomponents React MCP Server, which means it retrieves data without modifying state.
create_app accepts 2 parameters: appName, template. Required: appName, template. 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 create_app: 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.
create_app 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 create_app 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 create_app. 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.
create_app 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.