Undeploy an artifact from the SAP CPI runtime.
AI agents call undeploy_artifact to permanently remove resources in Mcp Sap Cpi — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Undeploying an artifact from a production integration platform stops all in-flight and future message processing for that artifact. This cannot be automatically undone (re-deployment is a separate manual step) and can cause service outages, making it Destructive with high severity given the blast radius in a live SAP CPI environment.
From the tool's definition 'Undeploy an artifact from the SAP CPI runtime' — removing a deployed integration artifact from the runtime is an irreversible operational action that immediately halts message processing for that artifact.
Attacks that exploit this kind of access
Undeploy an artifact from the SAP CPI runtime. It is categorised as a Destructive tool in the Mcp Sap Cpi MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Sap Cpi MCP server in PolicyLayer and add a rule for undeploy_artifact: 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 Sap Cpi. Nothing to install.
undeploy_artifact 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 undeploy_artifact 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 undeploy_artifact. 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.
undeploy_artifact is provided by the Mcp Sap Cpi MCP server (keelside/mcp-sap-cpi). 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 →