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.

SERVERElementify MCP SOURCEvamerli/elementify-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/vamerli-elementify-mcp/compose-page-from-templates.md

WHAT IT DOES

What compose_page_from_templates does on Elementify MCP

AI agents call compose_page_from_templates to retrieve information from Elementify MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why compose_page_from_templates is rated Low

Even though compose_page_from_templates only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

compose_page_from_templates is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "compose_page_from_templates": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about compose_page_from_templates

What does the compose_page_from_templates tool do? +

How do I enforce a policy on compose_page_from_templates? +

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.

What risk level is compose_page_from_templates? +

compose_page_from_templates is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit compose_page_from_templates? +

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.

How do I block compose_page_from_templates completely? +

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.

What MCP server provides compose_page_from_templates? +

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.

KEEP EXPLORING

More on Elementify, and thousands of servers like it.

This server

All 254 Elementify tools →

Across the catalogue

extract_text_from_image on Percepta MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →