List available Elasticsearch indices.
AI agents call list_indices to retrieve information from Odigo Elastic S2l without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward metadata query operation that retrieves information about available Elasticsearch indices. It has no side effects, cannot modify data, and presents minimal risk. The blast radius of misuse is extremely limited—an attacker gains only knowledge of what indices exist in the cluster, which is informational only. Classified as Read with low severity.
From the tool's definition Tool name 'list_indices' and description 'List available Elasticsearch indices' indicate a simple retrieval operation with no data modification or deletion capability.
Attacks that exploit this kind of access
List available Elasticsearch indices. It is categorised as a Read tool in the Odigo Elastic S2l MCP Server, which means it retrieves data without modifying state.
Register the Odigo Elastic S2l MCP server in PolicyLayer and add a rule for list_indices: 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 Odigo Elastic S2l. Nothing to install.
list_indices 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 list_indices 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 list_indices. 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.
list_indices is provided by the Odigo Elastic S2l MCP server (rbeg1/odigo-elastic-s2l-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →