recommend_indexes_account
AI agents call recommend_indexes_account 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.
The name pattern 'recommend_*' generally indicates a tool that generates suggestions or reports based on existing data analysis, which is a read operation. No description was provided, which lowers confidence. The tool would likely query account index metrics and suggest optimizations without modifying data.
From the tool's definition Tool name 'recommend_indexes_account' suggests an advisory/analytical operation that examines account index usage patterns; description is empty but the verb 'recommend' typically indicates read-only analysis without side effects.
Attacks that exploit this kind of access
recommend_indexes_account. 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 recommend_indexes_account: 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.
recommend_indexes_account 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 recommend_indexes_account 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 recommend_indexes_account. 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.
recommend_indexes_account 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.