Search for nodes in the knowledge graph based on a query
AI agents call search_nodes to retrieve information from WebDAV MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search operation on existing data within a knowledge graph. Searching is a read-only operation that retrieves information without causing side effects, data modification, or irreversible changes. The blast radius of misuse is minimal—an agent could only retrieve data it is already authorized to access through the server.
From the tool's definition Tool name 'search_nodes' and description 'Search for nodes in the knowledge graph based on a query' indicate retrieval/query operations with no modification or deletion of data.
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 WebDAV MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WebDAV MCP Server 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 WebDAV MCP Server. 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 WebDAV MCP Server MCP server (masx200/mcp-webdav-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 →