search_posts

A read tool on the WordPress MCP server.

SERVERWordPress MCP Server SOURCEbeilunyang/wordpress-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/beilunyang-wordpress-mcp-server/search-posts.md

WHAT IT DOES

What search_posts does on WordPress MCP Server

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

RISK

Why search_posts is rated Low

Search operations retrieve data without modifying or deleting anything. The absence of parameters that would indicate side effects, combined with the naming convention and peer tools on the server, strongly suggests this is a non-destructive query. Risk is low because misuse would only expose existing post data, not cause irreversible harm.

From the tool's definition Tool name 'search_posts' indicates a query/retrieval operation. The server context describes content management via REST API.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

search_posts Allowed

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

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

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

FAQ

Questions about search_posts

What does the search_posts tool do? +

search_posts is a read tool on the WordPress MCP Server MCP server. 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 search_posts? +

Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for search_posts: 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 search_posts? +

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

Can I rate-limit search_posts? +

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

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

search_posts is provided by the WordPress MCP Server MCP server (beilunyang/wordpress-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on WordPress MCP Server, and thousands of servers like it.

This server

All 4 WordPress MCP Server tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

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