Lists workflow execution history with details on success/failure status, duration, and timestamps. Use this tool to monitor workflow performance, troubleshoot issues, or verify that workflows are running as expected. Results can be filtered by workflow ID, status, and limited to a specific number.
AI agents call list_executions to retrieve information from Mcp N8n Builder 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 execution data with optional filtering. It has no side effects—it does not modify workflows, trigger executions, delete data, or commit financial obligations. The primary purpose is visibility and diagnostics, which are characteristic of Read category tools. The low severity reflects minimal blast radius if misused by an AI agent.
From the tool's definition Tool description explicitly states it 'Lists workflow execution history' and enables monitoring/troubleshooting without modification. Key verbs are passive retrieval operations ('Lists', 'monitor', 'verify'). Results are 'filtered' but not altered.
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 Mcp N8n Builder, 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.
Lists workflow execution history with details on success/failure status, duration, and timestamps. Use this tool to monitor workflow performance, troubleshoot issues, or verify that workflows are running as expected. Results can be filtered by workflow ID, status, and limited to a specific number. It is categorised as a Read tool in the Mcp N8n Builder MCP Server, which means it retrieves data without modifying state.
Register the Mcp N8n Builder 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 Mcp N8n Builder. 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 Mcp N8n Builder MCP server (spences10/mcp-n8n-builder). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Mcp N8n Builder tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 Mcp N8n Builder tools catalogued and risk-classified — across an index of 42,500+ MCP servers.