Search documents in Elasticsearch index with advanced filtering, pagination, and time-based sorting capabilities
AI agents call search to retrieve information from Agent Knowledge MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs document queries and retrieval from an Elasticsearch index. It uses standard search parameters (filtering, pagination, sorting) to query existing data without creating, modifying, deleting, or executing code. This is a pure read operation with minimal security risk; the worst outcome of misuse would be unauthorized information disclosure limited by index access controls.
From the tool's definition Tool name 'search' and description explicitly states it 'Search documents in Elasticsearch index with advanced filtering, pagination, and time-based sorting capabilities' — a retrieval operation with no data modification or side effects.
Documented attack patterns abuse exactly the kind of access search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agent Knowledge MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search:
{
"version": "1",
"default": "deny",
"tools": {
"search": {}
}
}search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search documents in Elasticsearch index with advanced filtering, pagination, and time-based sorting capabilities. It is categorised as a Read tool in the Agent Knowledge MCP MCP Server, which means it retrieves data without modifying state.
Register the Agent Knowledge 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 Agent Knowledge MCP. 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 Agent Knowledge MCP server (itshare4u/agentknowledgemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agent Knowledge MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
27 Agent Knowledge MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.