📊 Explain why a template matches your query.
AI agents call explain_template_match 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 information about template matching—it explains reasoning behind matches. It has no side effects: it does not create, modify, execute, delete, or move data. It is a read-only analytical tool that provides insights to the user. The blast radius of misuse is minimal (unwanted information disclosure) compared to tools that modify or execute workflows.
From the tool's definition Tool name 'explain_template_match' and description '📊 Explain why a template matches your query' indicate a retrieval and informational operation that provides analysis or matching explanation without modifying, executing, or deleting any workflow data.
Attacks that exploit this kind of access
📊 Explain why a template matches your query. 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 explain_template_match: 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.
explain_template_match 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 explain_template_match 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 explain_template_match. 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.
explain_template_match 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.
explain_template_match is one line of n8n Workflow Builder's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →