Perform an Elasticsearch search with the provided query DSL, highlighting, and script fields
AI agents call search to retrieve information from Octodet Elasticsearch without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The search tool executes read-only Elasticsearch queries. While it processes a query DSL and can use script fields, these are used to retrieve and format results, not to modify data. The absence of create, update, delete, or write operations in the description, combined with the explicit 'search' operation, confirms this is a Read category tool.
From the tool's definition Tool name 'search' and description 'Perform an Elasticsearch search with the provided query DSL, highlighting, and script fields' indicates a query operation that retrieves data without modifying it.
Attacks that exploit this kind of access
Perform an Elasticsearch search with the provided query DSL, highlighting, and script fields. It is categorised as a Read tool in the Octodet Elasticsearch MCP Server, which means it retrieves data without modifying state.
Register the Octodet Elasticsearch MCP server in PolicyLayer and add a rule for search: 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.
search 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 search 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 search. 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.
search 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 →