migrate_workflow · n8n Workflow Builder MCP: Risk & Policy

WHAT IT DOES

What migrate_workflow does on n8n Workflow Builder

AI agents use migrate_workflow to create or update resources in n8n Workflow Builder — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your n8n Workflow Builder environment.

WHY IT NEEDS A POLICY

Why migrate_workflow needs a policy

This tool modifies existing workflows by updating node versions, falling under the Write category as it creates/modifies data reversibly. While migrations can have unintended side effects if version upgrades introduce breaking changes, the action itself is not inherently destructive or irreversible—workflows can be reverted to previous versions or re-migrated.

From the tool's definition Tool name 'migrate_workflow' and description state 'Automatically migrate workflow to latest node versions.' The action modifies workflow configuration by updating node versions, which is a reversible change to stored workflow data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

migrate_workflow Rate-limited

migrate_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "migrate_workflow": {
      "limits": [
        {
          "counter": "migrate_workflow_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 Workflow Builder, so you can run agents against it safely.

FAQ

Questions about migrate_workflow

What does the migrate_workflow tool do? +

🔄 Automatically migrate workflow to latest node versions. It is categorised as a Write tool in the n8n Workflow Builder MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on migrate_workflow? +

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

What risk level is migrate_workflow? +

migrate_workflow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit migrate_workflow? +

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

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

migrate_workflow is provided by the n8n Workflow Builder MCP server (schimmilab/n8n-workflow-builder). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.