KendraQueryTool
AI agents call KendraQueryTool to retrieve information from AWS IoT SiteWise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
While the description is empty, reducing confidence, the tool name strongly suggests querying a knowledge index. Query tools are typically Read operations—they retrieve data without modifying state. However, AWS Kendra queries can be computationally expensive and could be abused to cause resource exhaustion, raising severity to medium rather than low.
From the tool's definition Tool name 'KendraQueryTool' and sibling tool names like 'aggregate' and 'analyze_*' indicate data retrieval and analysis operations.
Attacks that exploit this kind of access
KendraQueryTool. It is categorised as a Read tool in the AWS IoT SiteWise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS IoT SiteWise MCP Server 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 AWS IoT SiteWise MCP Server. 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 AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.