Search WordPress posts by keyword in title and content.
AI agents call wordpress_search_posts to retrieve information from MCP Wordpress without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing WordPress posts based on search criteria. It does not create, modify, delete, or execute any operations—it only returns matching data. The blast radius is minimal: incorrect search results could mislead an agent, but no data is at risk of modification or deletion.
From the tool's definition Tool name and description: 'Search WordPress posts by keyword in title and content.' The verb 'search' and the action of querying/retrieving posts without modification clearly indicate a read-only operation with no side effects.
Attacks that exploit this kind of access
Search WordPress posts by keyword in title and content. It is categorised as a Read tool in the MCP Wordpress MCP Server, which means it retrieves data without modifying state.
Register the MCP Wordpress MCP server in PolicyLayer and add a rule for wordpress_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 MCP Wordpress. Nothing to install.
wordpress_search_posts 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 wordpress_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.
Set action: deny in the PolicyLayer policy for wordpress_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.
wordpress_search_posts is provided by the MCP Wordpress MCP server (crunchtools/mcp-wordpress). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →