mcp_get_elementor_build
Get full Elementor page build (containers, widgets, settings tree) with element and widget counts
This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/mcp-get-elementor-build.md
What mcp_get_elementor_build does on Wordpress
AI agents call mcp_get_elementor_build to retrieve information from Wordpress without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mcp_get_elementor_build is rated Low
Retrieves page structure and configuration data without modifying or executing anything.
From the tool's definition Get full Elementor page build, containers, widgets, settings tree
Attacks that exploit this kind of access
The rule that runs mcp_get_elementor_build safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wordpress, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp_get_elementor_build, this is the rule to start with:
mcp_get_elementor_build is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Wordpress, apply this rule, and every mcp_get_elementor_build call is checked against it from then on.
Questions about mcp_get_elementor_build
Get full Elementor page build (containers, widgets, settings tree) with element and widget counts. It is categorised as a Read tool in the Wordpress MCP Server, which means it retrieves data without modifying state.
Register the Wordpress MCP server in PolicyLayer and add a rule for mcp_get_elementor_build: 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 Wordpress. Nothing to install.
mcp_get_elementor_build 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 mcp_get_elementor_build 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 mcp_get_elementor_build. 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.
mcp_get_elementor_build is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wordpress, and thousands of servers like it.
This server
Across the catalogue