wp_plugins_search

Search the WordPress plugin repository.

SERVERHostinger SOURCEidugeni/hostinger-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hostinger-mcp/wp-plugins-search.md

WHAT IT DOES

What wp_plugins_search does on Hostinger

AI agents call wp_plugins_search to retrieve information from Hostinger without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why wp_plugins_search is rated Low

This tool retrieves information from a public WordPress plugin repository without creating, modifying, deleting, or executing any code. It is a read-only search operation with no side effects or blast radius if misused by an AI agent.

From the tool's definition Tool name 'wp_plugins_search' and description 'Search the WordPress plugin repository' indicate a query/search operation with no modification or execution of code.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wp_plugins_search safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wp_plugins_search, this is the rule to start with:

wp_plugins_search Allowed

wp_plugins_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wp_plugins_search": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger, apply this rule, and every wp_plugins_search call is checked against it from then on.

FAQ

Questions about wp_plugins_search

What does the wp_plugins_search tool do? +

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

How do I enforce a policy on wp_plugins_search? +

Register the Hostinger MCP server in PolicyLayer and add a rule for wp_plugins_search: 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 Hostinger. Nothing to install.

What risk level is wp_plugins_search? +

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

Can I rate-limit wp_plugins_search? +

Yes. Add a rate_limit block to the wp_plugins_search 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 wp_plugins_search completely? +

Set action: deny in the PolicyLayer policy for wp_plugins_search. 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 wp_plugins_search? +

wp_plugins_search is provided by the Hostinger MCP server (idugeni/hostinger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hostinger, and thousands of servers like it.

This server

All 284 Hostinger tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →