This record as markdown: /tools/andhit-r-n8n-mcp/list-workflows.md
What list_workflows does on n8n MCP Server
AI agents call list_workflows to retrieve information from n8n MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_workflows is rated Low
List operations retrieve and enumerate data without modification. This is a standard read operation with minimal security risk unless the workflow list itself is sensitive, but listing is non-destructive and read-only. Low severity due to lack of side effects.
From the tool's definition Tool name 'list_workflows' indicates a retrieval operation. The description is empty, but the naming convention and sibling tool patterns (activate_workflow, create_workflow, etc.) establish that 'list_*' tools are queries. No side effects are implied.
Attacks that exploit this kind of access
The rule that runs list_workflows safely
PolicyLayer is an MCP gateway: it sits between your AI agents and n8n MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_workflows, this is the rule to start with:
list_workflows is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect n8n MCP Server, apply this rule, and every list_workflows call is checked against it from then on.
Questions about list_workflows
list_workflows is a read tool on the n8n MCP Server MCP server. It is categorised as a Read tool in the n8n MCP Server MCP Server, which means it retrieves data without modifying state.
Register the n8n 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 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 MCP Server MCP server (andhit-r/n8n-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on n8n MCP Server, and thousands of servers like it.
This server
Across the catalogue