search_with_query_string
AI agents call search_with_query_string to retrieve information from Elasticsearch MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name strongly suggests a search/query operation, consistent with the server's stated purpose of searching Elasticsearch indices. Sibling tools (list_indices, get_mappings, search, get_index_stats) are all read-oriented. However, Elasticsearch query strings can potentially be used for complex operations, and the empty description prevents certainty.
From the tool's definition Tool name 'search_with_query_string' and server description mentions 'searching' as a primary capability. Description is empty, lowering confidence.
Attacks that exploit this kind of access
search_with_query_string. It is categorised as a Read tool in the Elasticsearch MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Elasticsearch MCP Server MCP server in PolicyLayer and add a rule for search_with_query_string: 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 MCP Server. Nothing to install.
search_with_query_string 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_with_query_string 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_with_query_string. 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_with_query_string is provided by the Elasticsearch MCP Server MCP server (sajitsasi/es_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 →