List workflow executions
AI agents call execution_list to retrieve information from N8n Fabric without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about past workflow executions. It performs a read-only query of execution records with no ability to modify, delete, or trigger any operations. The blast radius of misuse is minimal—an attacker could view execution history and infer details about workflows, but cannot execute workflows, modify data, or cause destructive changes. Classified as Read with low severity.
From the tool's definition Tool name 'execution_list' and description 'List workflow executions' indicate a retrieval operation that queries execution history without modification or side effects.
Attacks that exploit this kind of access
List workflow executions. It is categorised as a Read tool in the N8n Fabric MCP Server, which means it retrieves data without modifying state.
Register the N8n Fabric MCP server in PolicyLayer and add a rule for execution_list: 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 Fabric. Nothing to install.
execution_list 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 execution_list 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 execution_list. 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.
execution_list is provided by the N8n Fabric MCP server (ry-ops/n8n-fabric). 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 →