🔍 Search n8n official documentation.
AI agents call search_n8n_docs to retrieve information from n8n Workflow Builder without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward documentation search utility. It queries existing documentation without modifying data, executing code, or triggering external operations. The only potential concern is whether search results could be abused to inform malicious workflow construction, but the tool itself performs no action beyond retrieving read-only reference material. Classification as Read with low severity is appropriate.
From the tool's definition Tool name 'search_n8n_docs' and description '🔍 Search n8n official documentation' indicate retrieval of static documentation content with no mutation, execution, or side effects.
Attacks that exploit this kind of access
🔍 Search n8n official documentation. It is categorised as a Read tool in the n8n Workflow Builder MCP Server, which means it retrieves data without modifying state.
Register the n8n Workflow Builder MCP server in PolicyLayer and add a rule for search_n8n_docs: 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 Workflow Builder. Nothing to install.
search_n8n_docs 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_n8n_docs 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_n8n_docs. 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_n8n_docs is provided by the n8n Workflow Builder MCP server (schimmilab/n8n-workflow-builder). 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 →