hosting_searchWordPressPluginsV1
Search the WordPress.org plugin directory for plugins available to install. Use the returned slug values with POST /api/hosting/v1/accounts/{username}/wordpress/{software}/plugins/install.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-searchwordpresspluginsv1.md
What hosting_searchWordPressPluginsV1 does on Hostinger Api
AI agents call hosting_searchWordPressPluginsV1 to retrieve information from Hostinger Api without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
search | string | Yes | Search term to match against plugin names. Minimum 3 characters. |
Parameters from the server's own tool schema.
Why hosting_searchWordPressPluginsV1 is rated Low
This tool performs a search/query against the WordPress.org plugin directory and returns information. It has no side effects—it does not install, modify, delete, or execute anything. It merely retrieves and presents data from an external directory. The mention of 'slug' values for use in POST requests to install plugins indicates this tool itself does not perform installation; it only provides the lookup capability.
From the tool's definition Tool name contains 'search' and description states it 'Search[es] the WordPress.org plugin directory' - a query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs hosting_searchWordPressPluginsV1 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger Api, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hosting_searchWordPressPluginsV1, this is the rule to start with:
hosting_searchWordPressPluginsV1 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every hosting_searchWordPressPluginsV1 call is checked against it from then on.
Questions about hosting_searchWordPressPluginsV1
Search the WordPress.org plugin directory for plugins available to install. Use the returned slug values with POST /api/hosting/v1/accounts/{username}/wordpress/{software}/plugins/install. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
hosting_searchWordPressPluginsV1 accepts 1 parameter: search. Required: search. The full parameter table on this page comes from the server's own tool schema.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for hosting_searchWordPressPluginsV1: 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 Api. Nothing to install.
hosting_searchWordPressPluginsV1 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 hosting_searchWordPressPluginsV1 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 hosting_searchWordPressPluginsV1. 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.
hosting_searchWordPressPluginsV1 is provided by the Hostinger Api MCP server (hostinger-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger Api, and thousands of servers like it.
This server
Across the catalogue