Generate a base UI5 OData feature scaffold (view/controller/manifest/i18n) from service metadata with dry-run safety.
AI agents use scaffold_ui5_odata_feature to create or update resources in MCP SAPUI5 Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP SAPUI5 Server environment.
The tool creates new files (view, controller, manifest, i18n) as part of a scaffold generation process. This is a Write operation — it creates new artifacts but does not delete or overwrite existing ones. The 'dry-run safety' mention implies actual writes occur when not in dry-run mode.
From the tool's definition Generate a base UI5 OData feature scaffold (view/controller/manifest/i18n) from service metadata with dry-run safety
Attacks that exploit this kind of access
Generate a base UI5 OData feature scaffold (view/controller/manifest/i18n) from service metadata with dry-run safety. It is categorised as a Write tool in the MCP SAPUI5 Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP SAPUI5 Server MCP server in PolicyLayer and add a rule for scaffold_ui5_odata_feature: 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 MCP SAPUI5 Server. Nothing to install.
scaffold_ui5_odata_feature is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the scaffold_ui5_odata_feature 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 scaffold_ui5_odata_feature. 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.
scaffold_ui5_odata_feature is provided by the MCP SAPUI5 Server MCP server (santiagosanmartinn/mcpui5server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →