List all workflows in the n8n instance with their names, IDs, and active status.
AI agents call n8n_list_workflows to retrieve information from Polybridge MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and displays information about existing workflows without creating, modifying, executing, or deleting any data. It is a pure read operation with minimal security impact; the worst case is information disclosure about available workflows in the n8n instance.
From the tool's definition Tool description states 'List all workflows' — a retrieval operation that queries metadata (names, IDs, active status) with no modification or execution of workflows.
Attacks that exploit this kind of access
List all workflows in the n8n instance with their names, IDs, and active status. It is categorised as a Read tool in the Polybridge MCP MCP Server, which means it retrieves data without modifying state.
Register the Polybridge MCP server in PolicyLayer and add a rule for n8n_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 Polybridge MCP. Nothing to install.
n8n_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 n8n_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 n8n_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.
n8n_list_workflows is provided by the Polybridge MCP server (madjeek-web/polybridge-mcp). 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 →