list_users
AI agents call list_users to retrieve information from Awslabs Valkey without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' prefix combined with 'users' subject strongly suggests this tool retrieves or enumerates user information without modifying state. Despite the empty description lowering confidence slightly, the naming pattern is unambiguous for a read operation. Listing users has minimal blast radius—it retrieves data already present without destructive, financial, or code-execution consequences.
From the tool's definition Tool name is 'list_users' which follows read-operation naming conventions (list, get, fetch). No description provided. The verb 'list' indicates querying/retrieval without side effects.
Attacks that exploit this kind of access
list_users. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for list_users: 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 Valkey. Nothing to install.
list_users 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 list_users 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 list_users. 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.
list_users is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.