📖 Generate comprehensive workflow explanation: purpose, data flow, dependencies, risks. Perfect for audit, onboarding, and documentation.
AI agents call explain_workflow 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 performs information retrieval and analysis of workflows to produce documentation and understanding. It has no side effects on the workflow itself, execution environment, or data. Even though it may surface security risks (via risk analysis), the tool itself only reads and explains—it does not execute code, modify workflows, delete data, or commit financial transactions.
From the tool's definition Tool 'explain_workflow' generates explanations of existing workflow purpose, data flow, dependencies, and risks.
Attacks that exploit this kind of access
📖 Generate comprehensive workflow explanation: purpose, data flow, dependencies, risks. Perfect for audit, onboarding, and 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 explain_workflow: 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_workflow 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_workflow 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_workflow. 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_workflow 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 →