search_plugin_repository

Search for plugins in the WordPress.org plugin repository

Server FluentCommunity Manager wplaunchify/fluent-community-mcp
Category Read
Risk class Low
Parameters 00 required

What search_plugin_repository does on FluentCommunity Manager

AI agents call search_plugin_repository to retrieve information from FluentCommunity Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why search_plugin_repository needs a policy

This tool retrieves information from a public plugin repository without modifying, executing, or deleting anything. It is a straightforward read operation with minimal risk. An AI agent misusing this tool could at worst perform excessive queries or information gathering, but cannot cause data loss, code execution, financial impact, or destructive changes.

From the tool's definition Tool description states 'Search for plugins in the WordPress.org plugin repository' — a query operation with no side effects. The verb 'search' and the target 'WordPress.org plugin repository' (a public, read-only resource) indicate data retrieval only.

Questions about search_plugin_repository

What does the search_plugin_repository tool do? +

Search for plugins in the WordPress.org plugin repository. It is categorised as a Read tool in the FluentCommunity Manager MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_plugin_repository? +

Register the FluentCommunity Manager 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 FluentCommunity Manager. Nothing to install.

What risk level is search_plugin_repository? +

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

Can I rate-limit search_plugin_repository? +

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.

How do I block search_plugin_repository completely? +

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.

What MCP server provides search_plugin_repository? +

search_plugin_repository is provided by the FluentCommunity Manager MCP server (wplaunchify/fluent-community-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.