KendraQueryTool
AI agents call KendraQueryTool 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.
Query tools are typically read-only operations that retrieve or search data without modifying state. The absence of descriptive text reduces confidence, but the naming convention strongly implies a search/query operation against Kendra's index. No evidence of write, delete, execution, or financial side effects. Classified as Read with low severity due to minimal blast radius of a query operation.
From the tool's definition Tool name 'KendraQueryTool' suggests a query operation typical of AWS Kendra (search service). The description is empty, which limits certainty.
Attacks that exploit this kind of access
KendraQueryTool. 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 KendraQueryTool: 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.
KendraQueryTool 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 KendraQueryTool 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 KendraQueryTool. 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.
KendraQueryTool 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.