elementor_get_widget
Holt die Details eines spezifischen Elementor-Widgets anhand seiner ID
This record as markdown: /tools/c-sakel-wp-mcp-server/elementor-get-widget.md
What elementor_get_widget does on WordPress MCP Server
AI agents call elementor_get_widget to retrieve information from WordPress MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why elementor_get_widget is rated Low
This tool retrieves widget configuration data by ID. The verb 'get/holt' and the absence of any modification, deletion, or execution language classify it as a Read operation. The blast radius is minimal—an AI agent can only view existing widget details, not alter or execute anything. Low severity reflects the read-only nature and limited impact of data exposure.
From the tool's definition Tool name 'elementor_get_widget' and description 'Holt die Details eines spezifischen Elementor-Widgets anhand seiner ID' (Gets the details of a specific Elementor widget by its ID) indicate a retrieval operation with no modification.
Attacks that exploit this kind of access
The rule that runs elementor_get_widget safely
PolicyLayer is an MCP gateway: it sits between your AI agents and WordPress MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For elementor_get_widget, this is the rule to start with:
elementor_get_widget 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 MCP Server, apply this rule, and every elementor_get_widget call is checked against it from then on.
Questions about elementor_get_widget
Holt die Details eines spezifischen Elementor-Widgets anhand seiner ID. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for elementor_get_widget: 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 MCP Server. Nothing to install.
elementor_get_widget 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 elementor_get_widget 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 elementor_get_widget. 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.
elementor_get_widget is provided by the WordPress MCP Server MCP server (c-sakel/wp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on WordPress MCP Server, and thousands of servers like it.
This server
Across the catalogue