set_random_member
Get random member(s) from set without removing. Args: key: The name of the key count: Number of members to return (optional) Returns: Random member(s) or error message
This record as markdown: /tools/aws/set-random-member.md
What set_random_member does on AWS
AI agents call set_random_member to retrieve information from AWS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why set_random_member is rated Low
This tool retrieves random members from a set without any modification or side effects. The description explicitly states 'without removing', confirming it is a pure read operation. Misuse has minimal blast radius as it only reads data.
From the tool's definition Get random member(s) from set without removing
Attacks that exploit this kind of access
The rule that runs set_random_member safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AWS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_random_member, this is the rule to start with:
set_random_member is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every set_random_member call is checked against it from then on.
Questions about set_random_member
Get random member(s) from set without removing. Args: key: The name of the key count: Number of members to return (optional) Returns: Random member(s) or error message. It is categorised as a Read tool in the AWS MCP Server, which means it retrieves data without modifying state.
Register the AWS MCP server in PolicyLayer and add a rule for set_random_member: 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. Nothing to install.
set_random_member is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the set_random_member 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_random_member. 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_random_member is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AWS, and thousands of servers like it.
This server
Across the catalogue