Perform an Elasticsearch search with the provided query DSL. Highlights are always enabled.
AI agents call search to retrieve information from Custom Elasticsearch MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data from Elasticsearch indices with no side effects—it does not create, modify, delete, or execute arbitrary code. However, severity is medium rather than low because: (1) search results could expose sensitive data if an agent queries without appropriate access controls or leaks results, (2) resource-intensive queries could cause denial-of-service or high latency on the cluster, and…
From the tool's definition Tool name 'search' and description 'Perform an Elasticsearch search' indicate data retrieval without modification. The phrase 'query DSL' confirms this executes search queries against existing data.
Attacks that exploit this kind of access
Perform an Elasticsearch search with the provided query DSL. Highlights are always enabled. It is categorised as a Read tool in the Custom Elasticsearch MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Custom Elasticsearch MCP Server 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 Custom Elasticsearch MCP Server. 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 Custom Elasticsearch MCP Server MCP server (m0-ar/custom-elasticsearch-mcp-server). 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 →