Low Risk

list_indices

List all indices in the Opensearch cluster

How to control list_indices ↓

What list_indices does on OpenSearch MCP Server

AI agents call list_indices to retrieve information from OpenSearch MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_indices needs a policy

This tool performs a read-only operation that enumerates indices in the cluster. It has no side effects, does not execute code, and does not modify, delete, or commit financial transactions. The blast radius of misuse is minimal—an attacker gains visibility into cluster structure but cannot directly compromise data or systems. Confidence is high because the intent and function are unambiguous.

From the tool's definition Tool name 'list_indices' and description 'List all indices in the Opensearch cluster' indicate a query operation that retrieves metadata about existing indices without modifying or deleting data.

Documented attack patterns abuse exactly the kind of access list_indices gives an agent:

How to control list_indices

PolicyLayer is an MCP gateway — it sits between your AI agents and OpenSearch MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_indices:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_indices": {}
  }
}

list_indices is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register OpenSearch MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_indices

What does the list_indices tool do? +

List all indices in the Opensearch cluster. It is categorised as a Read tool in the OpenSearch MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_indices? +

Register the OpenSearch MCP Server 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 OpenSearch MCP Server. Nothing to install.

What risk level is list_indices? +

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

Can I rate-limit list_indices? +

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.

How do I block list_indices completely? +

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.

What MCP server provides list_indices? +

list_indices is provided by the OpenSearch MCP Server MCP server (seohyunjun/opensearch-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OpenSearch MCP Server tool call.

Start from OpenSearch MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

14 OpenSearch MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.