List workflow executions
AI agents call n8n_list_executions to retrieve information from n8n 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 and queries historical workflow execution data. It does not create, modify, delete, or execute workflows—it only retrieves information about past executions. This is a standard read operation with minimal risk. Even if an AI agent misuses this tool, it cannot cause harm beyond information disclosure of execution logs, which would have low impact on system integrity or operations.
From the tool's definition Tool name is 'n8n_list_executions' and description states 'List workflow executions'. The verb 'list' and the action of retrieving execution records are clearly read-only operations with no side effects.
Attacks that exploit this kind of access
List workflow executions. 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 n8n_list_executions: 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.
n8n_list_executions 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_executions 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_executions. 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_executions is provided by the n8n MCP Server MCP server (shravan1610/n8n-mcp-server). 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 →