index_document · Elasticsearch/OpenSearch MCP Server MCP

WHAT IT DOES

What index_document does on Elasticsearch/OpenSearch MCP Server

AI agents use index_document to create or update resources in Elasticsearch/OpenSearch MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Elasticsearch/OpenSearch MCP Server environment.

WHY IT NEEDS A POLICY

Why index_document needs a policy

This tool creates new documents or updates existing ones in an Elasticsearch/OpenSearch index. This is a reversible write operation — documents can be deleted or overwritten after the fact. It does not execute code, delete data, or move money, so Write is the most appropriate category. Severity is medium because misuse could overwrite important documents or inject malicious data into the index.

From the tool's definition Creates or updates a document in the index

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

index_document Rate-limited

index_document stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "index_document": {
      "limits": [
        {
          "counter": "index_document_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Elasticsearch/OpenSearch MCP Server, so you can run agents against it safely.

FAQ

Questions about index_document

What does the index_document tool do? +

Creates or updates a document in the index. It is categorised as a Write tool in the Elasticsearch/OpenSearch MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on index_document? +

Register the Elasticsearch/OpenSearch MCP Server MCP server in PolicyLayer and add a rule for index_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 Elasticsearch/OpenSearch MCP Server. Nothing to install.

What risk level is index_document? +

index_document is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit index_document? +

Yes. Add a rate_limit block to the index_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.

How do I block index_document completely? +

Set action: deny in the PolicyLayer policy for index_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.

What MCP server provides index_document? +

index_document is provided by the Elasticsearch/OpenSearch MCP Server MCP server (rbedoyag/elasticsearch-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.