Index, get, update, delete individual documents or bulk index.
AI agents call es_document 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.
While the tool also supports read (get), write (index, update), and execute operations, the inclusion of delete functionality makes it Destructive. Deleting documents from Elasticsearch indices cannot be undone and represents the most severe risk category applicable. The bulk operations amplify the blast radius, as a single misconfigured call could delete large volumes of data irreversibly.
From the tool's definition The description explicitly states the tool can 'delete' documents, and 'bulk index' suggests batch operations. The phrase 'delete individual documents or bulk' indicates irreversible data removal capabilities.
Attacks that exploit this kind of access
Index, get, update, delete individual documents or bulk index. 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_document: 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_document 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_document 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_document. 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_document 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.
es_document is one line of RedisNexus's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →