Get shard information for all or specific indices
AI agents call get_shards to retrieve information from Elasticsearch MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves operational metadata about how Elasticsearch distributes index data across shards. It performs no mutations, executions, or deletions—only queries existing state. The operation is passive and has no side effects, placing it squarely in the Read category with low severity since exposing shard metadata poses minimal risk compared to data access or destructive operations.
From the tool's definition Tool name 'get_shards' and description 'Get shard information for all or specific indices' indicate retrieval of metadata without modification. Shard information is structural/operational data about index distribution, analogous to a read-only status query.
Attacks that exploit this kind of access
Get shard information for all or specific indices. It is categorised as a Read tool in the Elasticsearch MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Elasticsearch MCP Server MCP server in PolicyLayer and add a rule for get_shards: 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 MCP Server. Nothing to install.
get_shards 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 get_shards 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 get_shards. 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.
get_shards is provided by the Elasticsearch MCP Server MCP server (rishab2404/mcp_es). 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 →