AI agents invoke trigger_n8n_webhook to trigger actions in Spline. 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.
This tool triggers an external webhook, which invokes external code/workflows in n8n. Webhook triggers are Execute-category actions because they initiate potentially complex operations outside the MCP server whose effects are determined by the downstream n8n workflow configuration.
From the tool's definition Tool 'trigger_n8n_webhook' with description 'Trigger an n8n webhook to update scene variables' performs an external operation (webhook invocation) that executes a workflow in n8n, an external automation platform.
Attacks that exploit this kind of access
Trigger an n8n webhook to update scene variables. It is categorised as a Execute tool in the Spline MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Spline MCP server in PolicyLayer and add a rule for trigger_n8n_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 Spline. Nothing to install.
trigger_n8n_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 trigger_n8n_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 trigger_n8n_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.
trigger_n8n_webhook is provided by the Spline MCP server (lesleslie/spline-mcp). 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 →