mcp_search_elementor

Search published Elementor-built posts for widgets, settings, or text in string setting values (case-insensitive)

SERVERWordpress SOURCE@cavort-it-systems/wordpress-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/io-github-cvrt-jh-wordpress-mcp/mcp-search-elementor.md

WHAT IT DOES

What mcp_search_elementor does on Wordpress

AI agents call mcp_search_elementor 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.

RISK

Why mcp_search_elementor is rated Low

Queries Elementor post data without modifying, deleting, or executing code.

From the tool's definition Search published posts for widgets, settings, or text

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mcp_search_elementor 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_search_elementor, this is the rule to start with:

mcp_search_elementor Allowed

mcp_search_elementor 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": {
    "mcp_search_elementor": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Wordpress, apply this rule, and every mcp_search_elementor call is checked against it from then on.

FAQ

Questions about mcp_search_elementor

What does the mcp_search_elementor tool do? +

Search published Elementor-built posts for widgets, settings, or text in string setting values (case-insensitive). It is categorised as a Read tool in the Wordpress MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mcp_search_elementor? +

Register the Wordpress MCP server in PolicyLayer and add a rule for mcp_search_elementor: 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.

What risk level is mcp_search_elementor? +

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

Can I rate-limit mcp_search_elementor? +

Yes. Add a rate_limit block to the mcp_search_elementor 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 mcp_search_elementor completely? +

Set action: deny in the PolicyLayer policy for mcp_search_elementor. 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 mcp_search_elementor? +

mcp_search_elementor 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.

KEEP EXPLORING

More on Wordpress, and thousands of servers like it.

This server

All 314 Wordpress tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

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