Fetch full execution details by execution ID.
AI agents call get_execution 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 execution details—a read-only operation that queries existing workflow execution data. It has no side effects, cannot modify or delete data, and does not execute code or trigger external operations. The blast radius is minimal since fetching execution logs/details cannot damage workflows or systems. The n8n server's safety-first design further supports this classification.
From the tool's definition Tool name 'get_execution' and description 'Fetch full execution details by execution ID' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Fetch full execution details by execution ID. 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 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 N8n Workflow Tester Safe. 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 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 →