This record as markdown: /tools/andhit-r-n8n-mcp/get-execution.md
What get_execution does on n8n MCP Server
AI agents call get_execution to retrieve information from n8n MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_execution is rated Low
This tool retrieves execution information from n8n, which is a non-destructive read operation. Even if the execution data contains sensitive information, the tool itself performs no side effects, creates no obligations, and does not execute or modify workflows. The blast radius of misuse is limited to information disclosure, making it a Read-category risk.
From the tool's definition Tool name 'get_execution' implies retrieval of execution data from n8n workflows. No description is provided, but the naming pattern aligns with query/fetch operations.
Attacks that exploit this kind of access
The rule that runs get_execution safely
PolicyLayer is an MCP gateway: it sits between your AI agents and n8n MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_execution, this is the rule to start with:
get_execution is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect n8n MCP Server, apply this rule, and every get_execution call is checked against it from then on.
Questions about get_execution
get_execution is a read tool on the n8n MCP Server MCP server. 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 (andhit-r/n8n-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on n8n MCP Server, and thousands of servers like it.
This server
Across the catalogue