compose_page_from_templates
Compose a new Elementor layout by merging sections from multiple templates — in order. For each source template you can optionally pick specific section indices; omitting sections takes all top-level elements. The composed layout can be saved as a new template, written directly to a page, or both.
This record as markdown: /tools/vamerli-elementify-mcp/compose-page-from-templates.md
What compose_page_from_templates does on Elementify MCP
AI agents use compose_page_from_templates 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 compose_page_from_templates is rated Medium
This tool creates new content (templates and/or pages) by merging existing templates, which is a Write operation. The severity is high because it can directly modify live WordPress pages and create new templates in bulk, with potentially wide site-wide impact if misused by an AI agent.
From the tool's definition compose a new Elementor layout by merging sections from multiple templates... saved as a new template, written directly to a page, or both
Attacks that exploit this kind of access
The rule that runs compose_page_from_templates 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 compose_page_from_templates, this is the rule to start with:
compose_page_from_templates 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 compose_page_from_templates call is checked against it from then on.
Questions about compose_page_from_templates
Compose a new Elementor layout by merging sections from multiple templates — in order. For each source template you can optionally pick specific section indices; omitting sections takes all top-level elements. The composed layout can be saved as a new template, written directly to a page, or both. 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 compose_page_from_templates: 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.
compose_page_from_templates 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 compose_page_from_templates 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 compose_page_from_templates. 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.
compose_page_from_templates 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