sorted_set_remove_by_lex

Remove members by lexicographical range.

Server Amazon SageMaker AI MCP Server awslabs.sagemaker-ai-mcp-server
Category Write
Risk class Medium
Parameters 00 required

What sorted_set_remove_by_lex does on Amazon SageMaker AI MCP Server

AI agents use sorted_set_remove_by_lex to create or update resources in Amazon SageMaker AI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon SageMaker AI MCP Server environment.

Why sorted_set_remove_by_lex needs a policy

The tool removes data from a set based on lexicographical ordering. While 'remove' suggests deletion, the scoping to a lexicographical range (rather than unconditional deletion) and the typical behavior of sorted set operations makes this reversible—removed members can theoretically be re-added. This classifies as Write rather than Destructive.

From the tool's definition Tool name 'sorted_set_remove_by_lex' contains the verb 'remove', and the description states 'Remove members by lexicographical range.' This indicates modification/deletion of set members based on a range condition.

Questions about sorted_set_remove_by_lex

What does the sorted_set_remove_by_lex tool do? +

Remove members by lexicographical range. It is categorised as a Write tool in the Amazon SageMaker AI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sorted_set_remove_by_lex? +

Register the Amazon SageMaker AI MCP Server 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 Amazon SageMaker AI MCP Server. Nothing to install.

What risk level is sorted_set_remove_by_lex? +

sorted_set_remove_by_lex is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

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 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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.