Search for plugins in the WordPress.org plugin repository
AI agents call search_plugin_repository to retrieve information from mcp-wordpress-instaWP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that retrieves information about available plugins from a public repository. No side effects, no data modification, no code execution. The blast radius of misuse is minimal—an AI agent might retrieve irrelevant plugin information but cannot cause harm through search alone.
From the tool's definition The tool description states it "Search[es] for plugins in the WordPress.org plugin repository," which is a query operation with no modification or execution of code.
Attacks that exploit this kind of access
Search for plugins in the WordPress.org plugin repository. It is categorised as a Read tool in the mcp-wordpress-instaWP MCP Server, which means it retrieves data without modifying state.
Register the mcp-wordpress-instaWP MCP server in PolicyLayer and add a rule for search_plugin_repository: 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-instaWP. Nothing to install.
search_plugin_repository 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_plugin_repository 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_plugin_repository. 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_plugin_repository is provided by the mcp-wordpress-instaWP MCP server (pace8/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 →