Download a workflow and save it to a local JSON file (avoids dumping to chat)
AI agents call download_workflow to retrieve information from n8n Workflow Builder MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves workflow data and exports it locally. It performs no side effects on the workflow itself—no creation, modification, activation, deletion, or execution occurs. Saving to a local file is a read operation that does not alter state on the n8n server or trigger external actions.
From the tool's definition Tool name 'download_workflow' and description 'Download a workflow and save it to a local JSON file' indicate data retrieval. The action is to fetch and export an existing workflow definition without modification, creation, or deletion.
Documented attack patterns abuse exactly the kind of access download_workflow gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and n8n Workflow Builder MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for download_workflow:
{
"version": "1",
"default": "deny",
"tools": {
"download_workflow": {}
}
} download_workflow is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Download a workflow and save it to a local JSON file (avoids dumping to chat). It is categorised as a Read tool in the n8n Workflow Builder MCP Server MCP Server, which means it retrieves data without modifying state.
Register the n8n Workflow Builder MCP Server MCP server in PolicyLayer and add a rule for download_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 MCP Server. Nothing to install.
download_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 download_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 download_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.
download_workflow is provided by the n8n Workflow Builder MCP Server MCP server (makafeli/n8n-workflow-builder). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from n8n Workflow Builder MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
34 n8n Workflow Builder MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.