AI agents call 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 lists historical execution data without side effects. It is a read-only operation that queries existing execution records. No data is created, modified, deleted, or executed. The low severity reflects that exposure of execution history could reveal workflow patterns or operational details, but poses minimal immediate risk.
From the tool's definition Tool name is 'list_executions' and description states 'Retrieve a list of workflow executions' - a pure query operation with no modification or execution of workflows.
Documented attack patterns abuse exactly the kind of access list_executions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and n8n MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_executions:
{
"version": "1",
"default": "deny",
"tools": {
"list_executions": {}
}
}list_executions 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.
Retrieve a list of workflow executions from n8n. 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_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.
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 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 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.
list_executions is provided by the n8n MCP Server MCP server (jacob-dietle/n8n-mcp-sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from n8n 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.
11 n8n MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.