Manage Elasticsearch indexes: list, create, delete, stats, mappings.
AI agents call es_index to permanently remove resources in RedisNexus — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although the tool also performs Read operations (list, stats, mappings) and Write operations (create), the ability to delete indexes makes this Destructive. Deletion is irreversible and represents the most severe capability. The blast radius is high because an AI agent could accidentally or maliciously delete critical production indexes, causing data loss and service disruption.
From the tool's definition The tool description explicitly states it can "delete" indexes, which is an irreversible operation. Elasticsearch index deletion destroys data that cannot be recovered without backups.
Attacks that exploit this kind of access
Manage Elasticsearch indexes: list, create, delete, stats, mappings. It is categorised as a Destructive tool in the RedisNexus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the RedisNexus MCP server in PolicyLayer and add a rule for es_index: 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 RedisNexus. Nothing to install.
es_index is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the es_index 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 es_index. 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.
es_index is provided by the RedisNexus MCP server (rajkumar-madhu/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 →