Retrieve execution history with status, timestamps, and workflow info. Filter by workflow ID or get all executions. Returns execution ID, status (success/error/running), start time, and workflow name. Use this to monitor automation performance or debug failures.
AI agents call n8n_list_executions to retrieve information from n8n Management MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely queries and retrieves historical data about workflow executions with no side effects. It is used for monitoring and debugging, which are read-only operations. No data is created, modified, deleted, or executed.
From the tool's definition Tool retrieves execution history with status, timestamps, and workflow info by filtering and returning data (execution ID, status, start time, workflow name) with no modification or deletion capabilities.
Attacks that exploit this kind of access
Retrieve execution history with status, timestamps, and workflow info. Filter by workflow ID or get all executions. Returns execution ID, status (success/error/running), start time, and workflow name. Use this to monitor automation performance or debug failures. It is categorised as a Read tool in the n8n Management MCP Server MCP Server, which means it retrieves data without modifying state.
Register the n8n Management 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 Management 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 Management MCP Server MCP server (node2flow-th/n8n-management-mcp-community). 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 →