Retrieves detailed information about a specific workflow execution, including execution time, status, and optionally the full data processed at each step. Particularly useful for debugging failed workflows or understanding data transformations between nodes.
AI agents call get_execution 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 performs a query operation that retrieves and displays existing execution data without creating, modifying, deleting, or executing any workflows. The blast radius is minimal as it only exposes historical execution information already stored in n8n. No side effects or state changes occur.
From the tool's definition Tool description states it 'Retrieves detailed information about a specific workflow execution' with focus on querying execution time, status, and data.
Documented attack patterns abuse exactly the kind of access get_execution 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 get_execution:
{
"version": "1",
"default": "deny",
"tools": {
"get_execution": {}
}
}get_execution 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.
Retrieves detailed information about a specific workflow execution, including execution time, status, and optionally the full data processed at each step. Particularly useful for debugging failed workflows or understanding data transformations between nodes. 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 get_execution: 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.
get_execution 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 get_execution 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 get_execution. 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.
get_execution 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.