This record as markdown: /tools/aws/client-list.md
What client_list does on AWS
AI agents call client_list 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 client_list is rated Low
This tool only retrieves a list of connected clients from a Valkey (Redis-compatible) server. It performs no modification, deletion, execution of arbitrary code, or financial operations. It is a straightforward read/query operation with minimal blast radius—knowledge of connected clients alone poses low risk unless combined with other attacks.
From the tool's definition Tool name 'client_list' and description 'Get a list of connected clients to the Valkey server' indicate a query operation that retrieves information without modifying state.
Attacks that exploit this kind of access
The rule that runs client_list 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 client_list, this is the rule to start with:
client_list 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 client_list call is checked against it from then on.
Questions about client_list
Get a list of connected clients to the Valkey server. 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 client_list: 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.
client_list 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 client_list 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 client_list. 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.
client_list 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