Search across all WordPress content types (posts, pages, categories, tags, media) in a single query. Returns matching results with their type, title, and URL.
AI agents call search_site to retrieve information from WordPress MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search query that retrieves and returns data about existing WordPress content without any side effects. It matches the Read category definition: retrieves or queries data with no side effects. The severity is low because misuse would only expose already-accessible content metadata rather than enabling destructive or financial harm.
From the tool's definition Tool description states it 'Search across all WordPress content types' and 'Returns matching results with their type, title, and URL' — purely a retrieval operation with no modification, deletion, or code execution capability.
Attacks that exploit this kind of access
Search across all WordPress content types (posts, pages, categories, tags, media) in a single query. Returns matching results with their type, title, and URL. 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 search_site: 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.
search_site 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 search_site 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 search_site. 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.
search_site is provided by the WordPress MCP Server MCP server (wolffcatskyy/wordpress-mcp). 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 →