Critical Risk →

sorted_set_remove_by_score

Remove members by score range.

How to control sorted_set_remove_by_score ↓

What sorted_set_remove_by_score does on Awslabs Amazon Sns Sqs

AI agents call sorted_set_remove_by_score to permanently remove resources in Awslabs Amazon Sns Sqs — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why sorted_set_remove_by_score needs a policy

The tool explicitly removes members from a sorted set based on a score range. Removal of data is irreversible (destructive), and a broad score range could wipe out large portions of data.

From the tool's definition 'Remove members by score range' — removes data irreversibly from a sorted set

Documented attack patterns abuse exactly the kind of access sorted_set_remove_by_score gives an agent:

How to control sorted_set_remove_by_score

PolicyLayer is an MCP gateway — it sits between your AI agents and Awslabs Amazon Sns Sqs, and nothing reaches the server without passing your rules. This is the rule we recommend for sorted_set_remove_by_score:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "sorted_set_remove_by_score"
  ]
}

sorted_set_remove_by_score disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Awslabs Amazon Sns Sqs — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about sorted_set_remove_by_score

What does the sorted_set_remove_by_score tool do? +

Remove members by score range. It is categorised as a Destructive tool in the Awslabs Amazon Sns Sqs 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_score? +

Register the Awslabs Amazon Sns Sqs MCP server in PolicyLayer and add a rule for sorted_set_remove_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 Awslabs Amazon Sns Sqs. Nothing to install.

What risk level is sorted_set_remove_by_score? +

sorted_set_remove_by_score 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_score? +

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

How do I block sorted_set_remove_by_score completely? +

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

What MCP server provides sorted_set_remove_by_score? +

sorted_set_remove_by_score is provided by the Awslabs Amazon Sns Sqs MCP server (awslabs.amazon-sns-sqs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Awslabs Amazon Sns Sqs tool call.

Start from Awslabs Amazon Sns Sqs, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

805 Awslabs Amazon Sns Sqs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.