elementor_common_widgets
Zeigt Beispielkonfigurationen für häufig verwendete Elementor Widgets
This record as markdown: /tools/c-sakel-wp-mcp-server/elementor-common-widgets.md
What elementor_common_widgets does on WordPress MCP Server
AI agents call elementor_common_widgets 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_common_widgets is rated Low
This tool appears to fetch or display pre-configured examples of Elementor widgets. It is informational and read-only in nature—it retrieves or presents configuration examples without modifying any WordPress data, executing code, or causing side effects. The German description confirms it 'shows' (zeigt) examples, not creates or modifies them. No destructive, financial, or execute-level actions are indicated.
From the tool's definition Tool name 'elementor_common_widgets' and description 'Zeigt Beispielkonfigurationen für häufig verwendete Elementor Widgets' (Shows example configurations for commonly used Elementor widgets) indicate the tool retrieves and displays example/reference data…
Attacks that exploit this kind of access
The rule that runs elementor_common_widgets 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_common_widgets, this is the rule to start with:
elementor_common_widgets 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_common_widgets call is checked against it from then on.
Questions about elementor_common_widgets
Zeigt Beispielkonfigurationen für häufig verwendete Elementor Widgets. 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_common_widgets: 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_common_widgets 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_common_widgets 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_common_widgets. 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_common_widgets 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