claudeus_wp_search__search
Universal search across all content. Search posts, pages, categories, tags, and other content types in a single request.
This record as markdown: /tools/deus-h-claudeus-wp-mcp/claudeus-wp-search--search.md
What claudeus_wp_search__search does on Claudeus WordPress MCP
AI agents call claudeus_wp_search__search to retrieve information from Claudeus WordPress MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why claudeus_wp_search__search is rated Low
The tool performs a search operation that queries and retrieves WordPress content. This is a retrieval action with no capacity to create, modify, delete, or execute code. The verb 'search' combined with the description emphasizing content retrieval across multiple types confirms this is a Read operation with minimal risk.
From the tool's definition Tool name 'search' and description 'Universal search across all content. Search posts, pages, categories, tags, and other content types in a single request' indicates a read-only query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs claudeus_wp_search__search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claudeus WordPress MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For claudeus_wp_search__search, this is the rule to start with:
claudeus_wp_search__search 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 Claudeus WordPress MCP, apply this rule, and every claudeus_wp_search__search call is checked against it from then on.
Questions about claudeus_wp_search__search
Universal search across all content. Search posts, pages, categories, tags, and other content types in a single request. It is categorised as a Read tool in the Claudeus WordPress MCP MCP Server, which means it retrieves data without modifying state.
Register the Claudeus WordPress MCP server in PolicyLayer and add a rule for claudeus_wp_search__search: 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 Claudeus WordPress MCP. Nothing to install.
claudeus_wp_search__search 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 claudeus_wp_search__search 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 claudeus_wp_search__search. 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.
claudeus_wp_search__search is provided by the Claudeus WordPress MCP server (deus-h/claudeus-wp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claudeus WordPress, and thousands of servers like it.
This server
Across the catalogue