Updates an existing workflow with new configuration. Typically used after retrieving a workflow with get_workflow, modifying its structure, and then saving the changes. The entire workflow structure must be provided, not just the parts being changed.
AI agents use update_workflow to create or update resources in Mcp N8n Builder — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp N8n Builder environment.
This tool modifies an existing n8n workflow by replacing its entire configuration. It's a Write operation (reversible update, not deletion), but carries high severity because overwriting an entire workflow structure could break automated business processes, disrupt integrations, or cause production workflows to malfunction if misused by an AI agent.
From the tool's definition Updates an existing workflow with new configuration... The entire workflow structure must be provided, not just the parts being changed.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access update_workflow gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp N8n Builder, and nothing reaches the server without passing your rules. This is the rule we recommend for update_workflow:
{
"version": "1",
"default": "deny",
"tools": {
"update_workflow": {
"limits": [
{
"counter": "update_workflow_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_workflow stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Updates an existing workflow with new configuration. Typically used after retrieving a workflow with get_workflow, modifying its structure, and then saving the changes. The entire workflow structure must be provided, not just the parts being changed. It is categorised as a Write tool in the Mcp N8n Builder MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp N8n Builder MCP server in PolicyLayer and add a rule for update_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 Mcp N8n Builder. Nothing to install.
update_workflow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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.
Set action: deny in the PolicyLayer policy for update_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.
update_workflow is provided by the Mcp N8n Builder MCP server (spences10/mcp-n8n-builder). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Mcp N8n Builder tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 Mcp N8n Builder tools catalogued and risk-classified — across an index of 42,500+ MCP servers.