migrate_form
Migrate forms between plugins: CF7 → Elementor Forms, WPForms → Elementor Forms, Gravity Forms → Elementor Forms. Preserves field structure and settings. Reports unmappable fields as warnings.
This record as markdown: /tools/vamerli-elementify-mcp/migrate-form.md
What migrate_form does on Elementify MCP
AI agents use migrate_form to create or update resources in Elementify MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Elementify MCP environment.
Why migrate_form is rated Medium
This tool performs data transformation and creation operations (migrating form structures and settings into Elementor Forms), making it a Write category action. Severity is high because form migration could affect form functionality, user submissions, and data handling across the WordPress environment.
From the tool's definition Tool migrates forms "between plugins" and "preserves field structure and settings," indicating it creates and modifies data in the destination plugin (Elementor Forms).
Attacks that exploit this kind of access
The rule that runs migrate_form safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Elementify MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For migrate_form, this is the rule to start with:
migrate_form 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Elementify MCP, apply this rule, and every migrate_form call is checked against it from then on.
Questions about migrate_form
Migrate forms between plugins: CF7 → Elementor Forms, WPForms → Elementor Forms, Gravity Forms → Elementor Forms. Preserves field structure and settings. Reports unmappable fields as warnings. It is categorised as a Write tool in the Elementify MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Elementify MCP server in PolicyLayer and add a rule for migrate_form: 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 Elementify MCP. Nothing to install.
migrate_form 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 migrate_form 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 migrate_form. 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.
migrate_form is provided by the Elementify MCP server (vamerli/elementify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Elementify, and thousands of servers like it.
This server
Across the catalogue