policy_list
AI agents call policy_list 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.
Policy listing is a read-only operation that retrieves existing policies without modification or deletion. The context of an AWS ElastiCache/MemoryDB server with related tools like 'add_user_to_group' and 'add_inline_policy' suggests this is a complementary query operation. Without evidence of side effects, execute capability, or destructive behavior, Read is the appropriate category.
From the tool's definition Tool name 'policy_list' suggests enumeration/retrieval of policies. The naming convention parallels other list operations common in AWS API tools (e.g., list_users, list_groups).
Attacks that exploit this kind of access
policy_list. 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 policy_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 Awslabs Valkey. Nothing to install.
policy_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 policy_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 policy_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.
policy_list 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.