AI agents call search_node_properties to retrieve information from n8n-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information about node properties without modifying data, executing workflows, or triggering external operations. It is a pure information lookup tool, comparable to a documentation search or schema inspection utility.
From the tool's definition Tool name is 'search_node_properties' and description states it 'Find[s] specific properties in a node' and 'Returns paths and descriptions.' The verb 'find' and 'returns' indicate a retrieval operation with no modification or execution of workflows.
Attacks that exploit this kind of access
Find specific properties in a node (auth, headers, body, etc). Returns paths and descriptions. It is categorised as a Read tool in the n8n-MCP MCP Server, which means it retrieves data without modifying state.
Register the n8n- MCP server in PolicyLayer and add a rule for search_node_properties: 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. Nothing to install.
search_node_properties 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_node_properties 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_node_properties. 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_node_properties is provided by the n8n- MCP server (mohsin-zaheer/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 →