List all aliases.
AI agents call list_aliases to retrieve information from Elasticsearch/OpenSearch MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and enumerates alias configurations from the Elasticsearch/OpenSearch cluster. This is a pure query operation that does not modify, create, or destroy any data or indices. Listing aliases is informational and has no blast radius if invoked by an AI agent.
From the tool's definition Tool name 'list_aliases' and description 'List all aliases' indicate a retrieval operation with no side effects. Aliases are metadata about index configurations, not data mutation or deletion.
Attacks that exploit this kind of access
List all aliases. It is categorised as a Read tool in the Elasticsearch/OpenSearch MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Elasticsearch/OpenSearch MCP Server MCP server in PolicyLayer and add a rule for list_aliases: 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 Elasticsearch/OpenSearch MCP Server. Nothing to install.
list_aliases 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_aliases 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_aliases. 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_aliases is provided by the Elasticsearch/OpenSearch MCP Server MCP server (rbedoyag/elasticsearch-mcp-server). 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 →