Add a new document to a specific Elasticsearch index
AI agents use add_document to create or update resources in Octodet Elasticsearch — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Octodet Elasticsearch environment.
The tool adds (creates) documents to an index, which is a reversible write operation. It does not delete, destroy, or execute arbitrary code. While it modifies state, the operation can be undone by deleting the document. Severity is medium because bulk document creation could impact system performance or data integrity if misused by an agent, but the operation itself is reversible.
From the tool's definition Tool description states 'Add a new document to a specific Elasticsearch index' — this creates new data in the index.
Attacks that exploit this kind of access
Add a new document to a specific Elasticsearch index. It is categorised as a Write tool in the Octodet Elasticsearch MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Octodet Elasticsearch MCP server in PolicyLayer and add a rule for add_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 Octodet Elasticsearch. Nothing to install.
add_document is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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 add_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.
add_document is provided by the Octodet Elasticsearch MCP server (octodet/elasticsearch-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 →