delete_app
AI agents call delete_app to permanently remove resources in Amazon SageMaker AI MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete_app' tool performs an irreversible operation that removes application resources, preventing recovery without external means. In SageMaker, deleting an app (such as a Jupyter notebook instance or Studio app) is a one-way action. This is categorized as Destructive rather than Write due to its irreversible nature.
From the tool's definition Tool name 'delete_app' indicates deletion of an application resource. In SageMaker context, this likely permanently removes a SageMaker app instance. The empty description limits full certainty, but the verb 'delete' is unambiguously destructive.
Attacks that exploit this kind of access
delete_app. It is categorised as a Destructive tool in the Amazon SageMaker AI MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Amazon SageMaker AI MCP Server MCP server in PolicyLayer and add a rule for delete_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 Amazon SageMaker AI MCP Server. Nothing to install.
delete_app 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 delete_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 delete_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.
delete_app is provided by the Amazon SageMaker AI MCP Server MCP server (awslabs.sagemaker-ai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.