Поиск узлов по названию или описанию.
AI agents call search_nodes to retrieve information from n8n MCP Server 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 node information (by name or description) without side effects. It is analogous to sibling tools like 'get_node_info', 'get_nodes_by_category', and 'list_node_categories', all of which are read-only operations. Even in the context of an n8n automation server, searching/discovering available nodes does not modify workflows, execute code, delete data, or commit financial actions.
From the tool's definition Tool name 'search_nodes' combined with description 'Поиск узлов по названию или описанию' (Search nodes by name or description) indicates a query/search operation. No creation, modification, execution, or deletion occurs.
Attacks that exploit this kind of access
Поиск узлов по названию или описанию. It is categorised as a Read tool in the n8n MCP Server MCP Server, which means it retrieves data without modifying state.
Register the n8n 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 n8n 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 n8n MCP Server MCP server (ospray-creator/n8n-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 →