rest_api_search

Durchsucht alle WordPress-Inhalte (Posts, Pages, Terms, etc.)

SERVERWordPress MCP Server SOURCEc-sakel/wp-mcp-server
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/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.

Questions about rest_api_search

What does the rest_api_search tool do? +

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.

How do I enforce a policy on rest_api_search? +

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.

What risk level is rest_api_search? +

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

Can I rate-limit rest_api_search? +

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.

How do I block rest_api_search completely? +

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.

What MCP server provides rest_api_search? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of WordPress MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.