AI agents call n8n_list_workflows to retrieve information from n8n-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries workflow metadata without creating, modifying, deleting, or executing anything. It is a read-only operation with minimal blast radius—exposing this to an AI agent poses only informational disclosure risks.
From the tool's definition Tool description states 'List workflows (minimal metadata only). Returns id/name/active/dates/tags.' with pagination support. The verb 'list' and 'returns' metadata indicate data retrieval with no side effects.
Attacks that exploit this kind of access
List workflows (minimal metadata only). Returns id/name/active/dates/tags. Check hasMore/nextCursor for pagination. It is categorised as a Read tool in the n8n-MCP MCP Server, which means it retrieves data without modifying state.
Register the n8n- 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 n8n-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 n8n- MCP server (mutahar456/n8n-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 →