List all workflows from your n8n instance. Returns a comprehensive list of all workflows with their IDs, names, status (active/inactive), creation dates, and basic metadata. Perfect for getting an overview of your automation landscape.
AI agents call list_workflows 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.
list_workflows retrieves and queries existing workflow data without side effects. It provides an overview of the automation landscape but does not create, modify, delete, or execute any workflows. This is a straightforward read operation that poses minimal risk even if misused by an AI agent.
From the tool's definition Tool is described as 'List all workflows' which 'Returns a comprehensive list' of workflows with metadata. The action is purely informational retrieval with no modification, creation, deletion, or execution of workflows.
Documented attack patterns abuse exactly the kind of access list_workflows 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 list_workflows:
{
"version": "1",
"default": "deny",
"tools": {
"list_workflows": {}
}
} list_workflows 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.
List all workflows from your n8n instance. Returns a comprehensive list of all workflows with their IDs, names, status (active/inactive), creation dates, and basic metadata. Perfect for getting an overview of your automation landscape. 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 list_workflows: 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.
list_workflows 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 list_workflows 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 list_workflows. 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.
list_workflows 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.