mcp-server

The server uses EJS templating for project generation, but templates and variables are internally controlled and validated (e.g., `appNamespace`, `frameworkVersion`, `author`). It executes `npm install` and `git init` in newly created, controlled directories, minimizing risk. Network requests to UI5 CDNs for API/version info are to trusted sources. The most significant network risk is fetching OData metadata via `oDataV4Url`, which is mitigated by a configurable domain allow list (`UI5_MCP_SERVER_ALLOWED_ODATA_DOMAINS`). Path inputs are normalized and validated against configured root paths to prevent traversal attacks. No direct usage of `eval` in the server's core logic, though underlying UI5 framework components might use it as noted in documentation.