🎯 Search templates using intent-based semantic matching.
AI agents call search_templates_by_intent 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 tool retrieves or queries template data based on semantic matching criteria. It does not create, modify, delete, or execute anything. The search operation has no side effects and simply returns matching results. This is a clear Read category operation with low severity since template search cannot harm systems or data.
From the tool's definition Tool name 'search_templates' and description 'Search templates using intent-based semantic matching' indicate a retrieval/query operation with no side effects. The action is purely informational—finding templates that match specified intent criteria.
Attacks that exploit this kind of access
🎯 Search templates using intent-based semantic matching. 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_templates_by_intent: 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_templates_by_intent 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_templates_by_intent 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_templates_by_intent. 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_templates_by_intent 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 →