Rollback a previously applied patch using stored backup metadata.
AI agents call rollback_project_patch to permanently remove resources in MCP SAPUI5 Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Rolling back a patch overwrites current file state with backup data, irreversibly undoing changes made since the patch was applied. Any work done after the patch application would be lost. This is effectively an overwrite/restore operation that cannot be undone without another backup, placing it in the Destructive category with high severity given it affects project-wide files.
From the tool's definition Rollback a previously applied patch using stored backup metadata
Attacks that exploit this kind of access
Rollback a previously applied patch using stored backup metadata. It is categorised as a Destructive tool in the MCP SAPUI5 Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP SAPUI5 Server MCP server in PolicyLayer and add a rule for rollback_project_patch: 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.
rollback_project_patch is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the rollback_project_patch 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 rollback_project_patch. 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.
rollback_project_patch 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.
rollback_project_patch is one line of MCP SAPUI5 Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →