Remove and return random member(s) from set.
AI agents use set_pop to create or update resources in Amazon Location Service MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon Location Service MCP Server environment.
The tool removes members from a set, which modifies data state but is reversible (the removed elements are returned and could be re-added). This is Write rather than Destructive because the operation is not permanent in an absolute sense—the removed data is still accessible/returned, and the original set can be reconstructed.
From the tool's definition Tool description states 'Remove and return random member(s) from set' — the 'Remove' action modifies a data structure by extracting and deleting elements, which is a Write operation (reversible modification).
Documented attack patterns abuse exactly the kind of access set_pop gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Location Service MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for set_pop:
{
"version": "1",
"default": "deny",
"tools": {
"set_pop": {
"limits": [
{
"counter": "set_pop_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_pop stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Remove and return random member(s) from set. It is categorised as a Write tool in the Amazon Location Service MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amazon Location Service 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 Location Service MCP Server. Nothing to install.
set_pop is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
set_pop is provided by the Amazon Location Service MCP Server MCP server (awslabs.aws-location-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon Location Service 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 Location Service MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.