New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

sorted_set_remove_by_lex

Remove members by lexicographical range. Args: key: The name of the key min_lex: Minimum value (inclusive) max_lex: Maximum value (inclusive) Returns: Success message or error message

SERVERAWS SOURCE@awslabs/mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/aws/sorted-set-remove-by-lex.md

What sorted_set_remove_by_lex does on AWS

AI agents call sorted_set_remove_by_lex to permanently remove resources in AWS, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why sorted_set_remove_by_lex is rated Critical

The tool removes data from a sorted set by lexicographical range. Removal of data is irreversible (members are deleted from the set), making this Destructive. The blast radius is medium since it affects a specific key's members but could remove many entries at once depending on the range specified.

From the tool's definition Remove members by lexicographical range

Questions about sorted_set_remove_by_lex

What does the sorted_set_remove_by_lex tool do? +

Remove members by lexicographical range. Args: key: The name of the key min_lex: Minimum value (inclusive) max_lex: Maximum value (inclusive) Returns: Success message or error message. It is categorised as a Destructive tool in the AWS MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on sorted_set_remove_by_lex? +

Register the AWS MCP server in PolicyLayer and add a rule for sorted_set_remove_by_lex: 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 AWS. Nothing to install.

What risk level is sorted_set_remove_by_lex? +

sorted_set_remove_by_lex is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit sorted_set_remove_by_lex? +

Yes. Add a rate_limit block to the sorted_set_remove_by_lex 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.

How do I block sorted_set_remove_by_lex completely? +

Set action: deny in the PolicyLayer policy for sorted_set_remove_by_lex. 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.

What MCP server provides sorted_set_remove_by_lex? +

sorted_set_remove_by_lex is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on AWS, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of AWS's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.