Critical Risk →

set_pop

Remove and return random member(s) from set.

How to control set_pop ↓

What set_pop does on Amazon ECS MCP Server

AI agents call set_pop to permanently remove resources in Amazon ECS MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why set_pop needs a policy

The tool removes members from a set, which is an irreversible deletion operation (the members are removed from the set). While this appears to be a Redis/cache set operation rather than a cloud infrastructure operation, removal of data without the ability to undo it classifies as Destructive.

From the tool's definition "Remove and return random member(s) from set"

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

How to control set_pop

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

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

set_pop 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 Amazon ECS MCP Server — 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 set_pop

What does the set_pop tool do? +

Remove and return random member(s) from set. It is categorised as a Destructive tool in the Amazon ECS MCP Server 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 set_pop? +

Register the Amazon ECS MCP Server MCP server in PolicyLayer and add a rule for set_pop: 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 ECS MCP Server. Nothing to install.

What risk level is set_pop? +

set_pop 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 set_pop? +

Yes. Add a rate_limit block to the set_pop 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 set_pop completely? +

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

set_pop is provided by the Amazon ECS MCP Server MCP server (awslabs.ecs-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 Amazon ECS MCP Server tool call.

Start from Amazon ECS MCP Server, 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 Amazon ECS MCP Server 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.