List all Elementor elements (sections, columns, widgets) on a page
AI agents call get_elementor_elements to retrieve information from Noleemits Vision Builder MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates existing page structure (sections, columns, widgets) without modifying, executing, or destroying any data. It is a pure read operation with minimal blast radius if misused — an AI agent could only query information already visible to an authorized WordPress user.
From the tool's definition Tool name includes 'get_' prefix and description states 'List all Elementor elements' — a query operation with no data modification, deletion, or execution of external code.
Attacks that exploit this kind of access
List all Elementor elements (sections, columns, widgets) on a page. It is categorised as a Read tool in the Noleemits Vision Builder MCP MCP Server, which means it retrieves data without modifying state.
Register the Noleemits Vision Builder MCP server in PolicyLayer and add a rule for get_elementor_elements: 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 Noleemits Vision Builder MCP. Nothing to install.
get_elementor_elements 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_elementor_elements 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_elementor_elements. 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_elementor_elements is provided by the Noleemits Vision Builder MCP server (noleemits/vision-builder-mcp). 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 →