search
AI agents call search 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.
Based on the server context (Elasticsearch interaction) and tool name 'search', this tool most likely performs read-only search/query operations against Elasticsearch indices. However, the empty description means we cannot rule out side effects. Classified as Read with medium severity since misuse could expose sensitive indexed data at scale.
From the tool's definition Tool name is 'search'; server description mentions 'searching' as a core capability alongside listing indices and retrieving mappings. Description is empty, lowering confidence.
Attacks that exploit this kind of access
search. 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: 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 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 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 →