n8n_test_workflow · n8n- MCP: Risk & Policy

WHAT IT DOES

What n8n_test_workflow does on n8n-MCP

AI agents invoke n8n_test_workflow to trigger actions in n8n-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why n8n_test_workflow needs a policy

This tool triggers actual workflow execution in n8n, which runs external operations whose effects depend on the workflow's contents. Since workflows can contain arbitrary actions (API calls, data modifications, notifications, etc.), triggering execution is an Execute-category action with high severity — a misused trigger could cause unintended side effects across many connected systems.

From the tool's definition Test/trigger workflow execution. Auto-detects trigger type (webhook/form/chat). Supports: webhook (HTTP), form (fields), chat (message).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

n8n_test_workflow Rate-limited

n8n_test_workflow stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "n8n_test_workflow": {
      "limits": [
        {
          "counter": "n8n_test_workflow_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches n8n-MCP, so you can run agents against it safely.

FAQ

Questions about n8n_test_workflow

What does the n8n_test_workflow tool do? +

Test/trigger workflow execution. Auto-detects trigger type (webhook/form/chat). Supports: webhook (HTTP), form (fields), chat (message). Note: Only workflows with these trigger types can be executed externally. It is categorised as a Execute tool in the n8n-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on n8n_test_workflow? +

Register the n8n- MCP server in PolicyLayer and add a rule for n8n_test_workflow: 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. Nothing to install.

What risk level is n8n_test_workflow? +

n8n_test_workflow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit n8n_test_workflow? +

Yes. Add a rate_limit block to the n8n_test_workflow 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 n8n_test_workflow completely? +

Set action: deny in the PolicyLayer policy for n8n_test_workflow. 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 n8n_test_workflow? +

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