get_execution

THE RISK

Low Risk

Why get_execution needs a policy

This tool fetches execution metadata and logs from a workflow run. It has no side effects, does not modify state, and does not trigger external operations. It is purely informational, making it a Read category tool with low severity since exposure poses minimal risk even if misused by an agent.

From the tool's definition Tool name is 'get_execution' and description states 'Retrieve detailed information about a specific workflow execution' — retrieve is a read-only operation that queries existing data without modification.

Documented attack patterns abuse exactly the kind of access get_execution gives an agent:

POLICY

How to control get_execution

PolicyLayer is an MCP gateway — it sits between your AI agents and n8n MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_execution:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_execution": {}
  }
}

get_execution is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register n8n MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More n8n MCP Server tools

Destructive delete_execution Delete a specific workflow execution from n8n Destructive delete_workflow Delete a workflow from n8n Execute run_webhook Execute a workflow via webhook with optional input data Write deactivate_workflow Deactivate a workflow in n8n Write activate_workflow Activate a workflow in n8n Write create_workflow Create a new workflow in n8n Write update_workflow Update an existing workflow in n8n Read get_workflow Retrieve a specific workflow by ID

All 11 n8n MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_execution

What does the get_execution tool do? +

Retrieve detailed information about a specific workflow execution. It is categorised as a Read tool in the n8n MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_execution? +

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.

What risk level is get_execution? +

get_execution is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_execution? +

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.

How do I block get_execution completely? +

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.

What MCP server provides get_execution? +

get_execution is provided by the n8n MCP Server MCP server (jacob-dietle/n8n-mcp-sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every n8n MCP Server tool call.

Start from n8n MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →