Get the result and status of a workflow execution by its execution ID.
AI agents call n8n_get_execution to retrieve information from Polybridge MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves the result and status of an already-completed workflow execution. It performs a read-only operation with no side effects—it does not create, modify, delete, or trigger any workflows. The data retrieval has minimal blast radius even if misused by an AI agent, as it only exposes information about past executions.
From the tool's definition Tool name 'n8n_get_execution' with description 'Get the result and status of a workflow execution' uses the verb 'get', which retrieves data without modifying or executing anything.
Attacks that exploit this kind of access
Get the result and status of a workflow execution by its execution ID. It is categorised as a Read tool in the Polybridge MCP MCP Server, which means it retrieves data without modifying state.
Register the Polybridge MCP server in PolicyLayer and add a rule for n8n_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 Polybridge MCP. Nothing to install.
n8n_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 n8n_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 n8n_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.
n8n_get_execution is provided by the Polybridge MCP server (madjeek-web/polybridge-mcp). 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 →