🔍 Get detailed error context for a failed execution. Extracts error node, simplifies error message, provides fix suggestions.
AI agents call get_execution_error_context to retrieve information from n8n Workflow Builder without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only diagnostic operations on existing execution data. It extracts information about past failures, simplifies messages, and suggests fixes—all non-destructive, side-effect-free operations. Retrieving execution error logs and providing suggestions does not alter state or trigger new operations.
From the tool's definition Tool retrieves detailed error context and error messages for failed executions. The description uses passive language: 'Extracts error node, simplifies error message, provides fix suggestions.' No create, modify, delete, execute, or financial operations are…
Attacks that exploit this kind of access
🔍 Get detailed error context for a failed execution. Extracts error node, simplifies error message, provides fix suggestions. It is categorised as a Read tool in the n8n Workflow Builder MCP Server, which means it retrieves data without modifying state.
Register the n8n Workflow Builder MCP server in PolicyLayer and add a rule for get_execution_error_context: 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 Builder. Nothing to install.
get_execution_error_context 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_error_context 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_error_context. 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_error_context is provided by the n8n Workflow Builder MCP server (schimmilab/n8n-workflow-builder). 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 →