sorted_set_range_by_score
AI agents call sorted_set_range_by_score as a supporting operation in AWS IoT SiteWise MCP Server workflows.
The tool name suggests a Redis-style sorted set range query operation (read/query by score), which would be a Read category. However, the description is completely empty, and the tool name does not clearly fit within the AWS IoT SiteWise domain. Without a description, confidence is very low.
From the tool's definition Tool name 'sorted_set_range_by_score' and empty description provide no context about what the tool does in the AWS IoT SiteWise MCP server context.
Attacks that exploit this kind of access
sorted_set_range_by_score. It is categorised as a Other tool in the AWS IoT SiteWise MCP Server MCP Server, which means it performs auxiliary operations.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for sorted_set_range_by_score: 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 IoT SiteWise MCP Server. Nothing to install.
sorted_set_range_by_score 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_score 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_score. 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_score is provided by the AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.