Return Elasticsearch cluster information.
AI agents call cluster_info 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 tool queries and returns metadata about an Elasticsearch cluster (status, version, nodes, etc.) without side effects. It is a pure read operation that retrieves information only, matching the 'Read' category definition of retrieving or querying data with no side effects. Severity is low because cluster information disclosure has minimal direct impact, though it could inform reconnaissance in a multi-step attack.
From the tool's definition Tool name 'cluster_info' and description 'Return Elasticsearch cluster information' indicate a data retrieval operation with no modification, deletion, or execution of arbitrary commands.
Attacks that exploit this kind of access
Return Elasticsearch cluster information. 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 cluster_info: 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.
cluster_info 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 cluster_info 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 cluster_info. 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.
cluster_info 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 →