sorted_set_range_by_lex
AI agents call sorted_set_range_by_lex as a supporting operation in Amazon MQ MCP Server workflows.
The description is empty and uninformative, making classification uncertain. The tool name 'sorted_set_range_by_lex' resembles a Redis read operation for retrieving elements from a sorted set by lexicographic range, which would be a Read. However, given the mismatch with the Amazon MQ server context and the lack of description, confidence is very low.
From the tool's definition Tool name 'sorted_set_range_by_lex' and empty description. The name suggests a Redis sorted set lexicographic range query operation (read), but this tool appears on an Amazon MQ server which manages AMQ brokers.
Attacks that exploit this kind of access
sorted_set_range_by_lex. It is categorised as a Other tool in the Amazon MQ MCP Server MCP Server, which means it performs auxiliary operations.
Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for sorted_set_range_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 MQ MCP Server. Nothing to install.
sorted_set_range_by_lex is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sorted_set_range_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.
Set action: deny in the PolicyLayer policy for sorted_set_range_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.
sorted_set_range_by_lex is provided by the Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.