delete_group
AI agents call delete_group 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.
Delete operations are classified as Destructive because they irreversibly remove data or resources and cannot be undone. In an AWS SageMaker/IAM context, deleting a group would remove user permissions and access configurations. The lack of description lowers confidence slightly, but the explicit 'delete' verb in the name makes the destructive intent clear.
From the tool's definition Tool name is 'delete_group' with no descriptive information provided. The verb 'delete' combined with the noun 'group' (likely an IAM or user group in AWS context) indicates irreversible removal of a resource.
Attacks that exploit this kind of access
delete_group. 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_group: 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_group 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_group 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_group. 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_group 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.