Get details of a specific execution
AI agents call get_execution to retrieve information from n8n MCP Server 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 from n8n workflows without modifying, deleting, or triggering any actions. It is a simple data query operation. Severity is low because reading execution metadata poses minimal risk; the information is already present in the system and no state changes occur. High confidence due to clear, unambiguous read-only semantics.
From the tool's definition Tool description states 'Get details of a specific execution' — a pure retrieval operation with no state modification or side effects. The verb 'Get' and lack of any mutating language confirm read-only behavior.
Attacks that exploit this kind of access
Get details of a specific execution. It is categorised as a Read tool in the n8n MCP Server MCP Server, which means it retrieves data without modifying state.
Register the n8n MCP Server 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 MCP Server. 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 MCP Server MCP server (nikolausm/n8n-mcp-server). 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 →