rest_api_search
Durchsucht alle WordPress-Inhalte (Posts, Pages, Terms, etc.)
This record as markdown: /tools/c-sakel-wp-mcp-server/rest-api-search.md
What rest_api_search does on WordPress MCP Server
AI agents call rest_api_search 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 rest_api_search is rated Low
This tool performs searches across WordPress content without modifying, deleting, or executing code. It retrieves and queries existing data (Posts, Pages, Terms) with no side effects. This is a classic Read operation with low blast radius—misuse would expose data already in the system, not cause irreversible changes or external effects.
From the tool's definition Tool name 'rest_api_search' and description 'Durchsucht alle WordPress-Inhalte (Posts, Pages, Terms, etc.)' [searches all WordPress content] indicate query/retrieval operations only.
Attacks that exploit this kind of access
The rule that runs rest_api_search 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 rest_api_search, this is the rule to start with:
rest_api_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 WordPress MCP Server, apply this rule, and every rest_api_search call is checked against it from then on.
Questions about rest_api_search
Durchsucht alle WordPress-Inhalte (Posts, Pages, Terms, etc.). 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 rest_api_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 WordPress MCP Server. Nothing to install.
rest_api_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 rest_api_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 rest_api_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.
rest_api_search 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