Trigger a workflow via its webhook URL. Use isTest=true for test webhooks. The webhookPath is the path configured in the Webhook node.
Part of the n8n MCP Server server.
Free to start. No card required.
AI agents invoke n8n_trigger_webhook to trigger processes or run actions in n8n MCP Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
n8n_trigger_webhook can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"n8n_trigger_webhook": {
"limits": [
{
"counter": "n8n_trigger_webhook_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full n8n MCP Server policy for all 43 tools.
These attack patterns abuse exactly the kind of access n8n_trigger_webhook gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Trigger a workflow via its webhook URL. Use isTest=true for test webhooks. The webhookPath is the path configured in the Webhook node.. It is categorised as a Execute tool in the n8n MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the n8n MCP Server MCP server in PolicyLayer and add a rule for n8n_trigger_webhook: 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.
n8n_trigger_webhook is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the n8n_trigger_webhook 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_trigger_webhook. 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_trigger_webhook is provided by the n8n MCP Server MCP server (@nextoolsolutions/mcp-n8n). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 43 n8n MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.