Medium Risk

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

Part of the Awslabs Valkey MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use sorted_set_remove_by_lex to create or modify resources in Awslabs Valkey. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call sorted_set_remove_by_lex repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Awslabs Valkey.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

amazon-elasticache-memorydb-valkey-mcp-server.yaml
tools:
  sorted_set_remove_by_lex:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Awslabs Valkey policy for all 105 tools.

Tool Name sorted_set_remove_by_lex
Category Write
Risk Level Medium

View all 105 tools →

Agents calling write-class tools like sorted_set_remove_by_lex have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

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 Write tool in the Awslabs Valkey 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? +

Add a rule in your Intercept YAML policy under the tools section for sorted_set_remove_by_lex. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Awslabs Valkey MCP server.

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 Intercept 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 Intercept 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 Awslabs Valkey MCP server (awslabs.valkey-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.