KendraListIndexesTool
AI agents call KendraListIndexesTool 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 strongly suggests this tool retrieves or queries a collection of Kendra search indexes without modifying them. This is a read-only operation with minimal blast radius. Confidence is moderate (0.7) due to empty description, but the naming convention is clear enough to classify as Read with low severity.
From the tool's definition Tool name 'KendraListIndexesTool' with 'List' verb indicates data retrieval operation. No description provided to confirm scope.
Attacks that exploit this kind of access
KendraListIndexesTool. 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 KendraListIndexesTool: 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.
KendraListIndexesTool 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 KendraListIndexesTool 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 KendraListIndexesTool. 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.
KendraListIndexesTool 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.