👁️ Preview what would change if workflow is migrated.
AI agents call get_migration_preview to retrieve information from n8n Workflow Builder without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about potential changes from a migration scenario without actually applying those changes. It has no side effects—it only reads and presents data. This is a classic Read operation: safe for inspection and analysis, with minimal risk if misused by an AI agent, as it cannot modify or delete workflows.
From the tool's definition Tool name 'get_migration_preview' and description '👁️ Preview what would change if workflow is migrated' indicate a preview/inspection operation. The verb 'preview' and 'get' denote retrieval without modification.
Attacks that exploit this kind of access
👁️ Preview what would change if workflow is migrated. It is categorised as a Read tool in the n8n Workflow Builder MCP Server, which means it retrieves data without modifying state.
Register the n8n Workflow Builder MCP server in PolicyLayer and add a rule for get_migration_preview: 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.
get_migration_preview is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_migration_preview 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 get_migration_preview. 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.
get_migration_preview 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.
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 →