Search for WordPress.org plugins by keyword
AI agents call search_plugins to retrieve information from WordPress Plugin Directory 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 against the WordPress.org plugin directory, returning matching results. It has no capability to modify, execute, or delete data. The operation is purely informational retrieval, which is the definition of a Read category tool.
From the tool's definition Tool name 'search_plugins' and description 'Search for WordPress.org plugins by keyword' indicate a query operation that retrieves information without modification or side effects.
Attacks that exploit this kind of access
Search for WordPress.org plugins by keyword. It is categorised as a Read tool in the WordPress Plugin Directory MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress Plugin Directory MCP Server MCP server in PolicyLayer and add a rule for search_plugins: 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 Plugin Directory MCP Server. Nothing to install.
search_plugins 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_plugins 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_plugins. 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_plugins is provided by the WordPress Plugin Directory MCP Server MCP server (juanma-wp/wordpress-org-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 →