Query the knowledge base for relevant documents.
AI agents call query_knowledge_base to retrieve information from ElasticMind-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries an Elasticsearch index to retrieve documents matching user search criteria. It performs semantic search and retrieval without creating, modifying, or deleting any data. The operation is read-only with no side effects, making it a standard Read category risk. Severity is low because misuse would only expose existing indexed information, not cause operational damage or enable other attacks.
From the tool's definition Tool name 'query_knowledge_base' and description 'Query the knowledge base for relevant documents' indicate a retrieval operation with no modification of underlying data.
Attacks that exploit this kind of access
Query the knowledge base for relevant documents. It is categorised as a Read tool in the ElasticMind-MCP MCP Server, which means it retrieves data without modifying state.
Register the ElasticMind- MCP server in PolicyLayer and add a rule for query_knowledge_base: 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 ElasticMind-MCP. Nothing to install.
query_knowledge_base 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 query_knowledge_base 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 query_knowledge_base. 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.
query_knowledge_base is provided by the ElasticMind- MCP server (viratgarg2/elasticmind-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 →