List recent executions, optionally filtered by workflowId and status.
AI agents call list_executions to retrieve information from N8n Workflow Tester Safe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries historical execution data without modifying, deleting, or executing anything. It is a pure read operation that returns information about past workflow runs. The filtering options (workflowId, status) are query parameters, not actions. The blast radius of misuse is minimal—an attacker could only gain visibility into execution history, not modify workflows, execute code, or cause damage.
From the tool's definition Tool name 'list_executions' and description 'List recent executions, optionally filtered by workflowId and status' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List recent executions, optionally filtered by workflowId and status. It is categorised as a Read tool in the N8n Workflow Tester Safe MCP Server, which means it retrieves data without modifying state.
Register the N8n Workflow Tester Safe 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 Workflow Tester Safe. 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 Workflow Tester Safe MCP server (souzix76/n8n-workflow-tester-safe). 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 →