Low Risk

recommend_indexes_account

Triage tool: find which log groups would benefit from field indexing. Scans the last 30 days of completed Logs Insights queries across the account, groups by log group, and identifies frequently queried but unindexed fields. Lightweight scan — no per-log-group Insights queries. Use recommend_ind...

Part of the AWS Labs CloudWatch MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call recommend_indexes_account to retrieve information from AWS Labs CloudWatch MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though recommend_indexes_account only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

aws-labs-cloudwatch-mcp-server.yaml
tools:
  recommend_indexes_account:
    rules:
      - action: allow

See the full AWS Labs CloudWatch MCP Server policy for all 19 tools.

Tool Name recommend_indexes_account
Category Read
Risk Level Low

View all 19 tools →

Agents calling read-class tools like recommend_indexes_account have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the recommend_indexes_account tool do? +

Triage tool: find which log groups would benefit from field indexing. Scans the last 30 days of completed Logs Insights queries across the account, groups by log group, and identifies frequently queried but unindexed fields. Lightweight scan — no per-log-group Insights queries. Use recommend_indexes_loggroup for full analysis on specific log groups.. It is categorised as a Read tool in the AWS Labs CloudWatch MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on recommend_indexes_account? +

Add a rule in your Intercept YAML policy under the tools section for recommend_indexes_account. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Labs CloudWatch MCP Server MCP server.

What risk level is recommend_indexes_account? +

recommend_indexes_account is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit recommend_indexes_account? +

Yes. Add a rate_limit block to the recommend_indexes_account rule in your Intercept 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.

How do I block recommend_indexes_account completely? +

Set action: deny in the Intercept 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.

What MCP server provides recommend_indexes_account? +

recommend_indexes_account is provided by the AWS Labs CloudWatch MCP Server MCP server (awslabs.cloudwatch-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.