Search for nodes in the knowledge graph based on a query
AI agents call search_nodes to retrieve information from Elastic Brain ZH without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data from the knowledge graph without side effects. It follows the Read category pattern of search/query operations. The blast radius of misuse is minimal—incorrect queries return wrong results but do not modify or destroy data.
From the tool's definition The tool name 'search_nodes' and description 'Search for nodes in the knowledge graph based on a query' indicate a retrieval operation with no data modification. The 'search' verb and query-based operation pattern are classic read operations.
Attacks that exploit this kind of access
Search for nodes in the knowledge graph based on a query. It is categorised as a Read tool in the Elastic Brain ZH MCP Server, which means it retrieves data without modifying state.
Register the Elastic Brain ZH MCP server in PolicyLayer and add a rule for search_nodes: 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 Elastic Brain ZH. Nothing to install.
search_nodes 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_nodes 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_nodes. 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_nodes is provided by the Elastic Brain ZH MCP server (tocharianou/elastic-brain-zh). 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 →