Replace an existing n8n workflow by ID with JSON.
AI agents use update_workflow to create or update resources in N8n Workflow Tester Safe — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your N8n Workflow Tester Safe environment.
This tool creates or modifies n8n workflow definitions, which is a reversible write operation. While the modification could have significant blast radius (misconfigured workflows could break automation processes or cause unintended side effects), it is not destructive (workflows can be reverted or re-updated) and does not delete data.
From the tool's definition Tool description states 'Replace an existing n8n workflow by ID with JSON' — this modifies/overwrites workflow definitions reversibly. The verb 'Replace' indicates data modification rather than deletion.
Attacks that exploit this kind of access
Replace an existing n8n workflow by ID with JSON. It is categorised as a Write tool in the N8n Workflow Tester Safe MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the N8n Workflow Tester Safe 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 N8n Workflow Tester Safe. 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 N8n Workflow Tester Safe MCP server (souzix76/n8n-workflow-tester-safe). 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 →