Remove members by rank range.
AI agents call sorted_set_remove_by_rank 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 tool removes (deletes) members from a sorted set by rank range. Removal of data is generally irreversible, placing it in the Destructive category. Severity is medium because it affects data within a specific data structure (sorted set) rather than broad system resources, but misuse could delete important indexed data.
From the tool's definition 'Remove members by rank range' — the word 'Remove' indicates irreversible deletion of data from a sorted set.
Attacks that exploit this kind of access
Remove members by rank range. 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 sorted_set_remove_by_rank: 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.
sorted_set_remove_by_rank 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 sorted_set_remove_by_rank 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 sorted_set_remove_by_rank. 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.
sorted_set_remove_by_rank 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.