hosting_listSuggestedWordPressPluginsV1
List curated plugin suggestions grouped by website type. 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-listsuggestedwordpresspluginsv1.md
What hosting_listSuggestedWordPressPluginsV1 does on Hostinger Api
AI agents call hosting_listSuggestedWordPressPluginsV1 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 |
|---|---|---|---|
order_id | integer | — | Optionally scope suggestions to a specific order. |
Parameters from the server's own tool schema.
Why hosting_listSuggestedWordPressPluginsV1 is rated Low
This tool performs a read-only retrieval of WordPress plugin suggestions grouped by website type. It has no side effects, does not create, modify, or delete data, and does not execute code or trigger financial transactions. It is purely a data query operation with minimal blast radius if an AI agent misuses it — the worst case would be retrieving an irrelevant list of plugins, which the user can ignore.
From the tool's definition Tool name contains 'list' and description states 'List curated plugin suggestions' — it retrieves and presents data without modification. The note about using `slug` values with a POST endpoint describes potential downstream usage, not the tool's own action.
Attacks that exploit this kind of access
The rule that runs hosting_listSuggestedWordPressPluginsV1 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_listSuggestedWordPressPluginsV1, this is the rule to start with:
hosting_listSuggestedWordPressPluginsV1 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_listSuggestedWordPressPluginsV1 call is checked against it from then on.
Questions about hosting_listSuggestedWordPressPluginsV1
List curated plugin suggestions grouped by website type. 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_listSuggestedWordPressPluginsV1 accepts 1 parameter: order_id. 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_listSuggestedWordPressPluginsV1: 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_listSuggestedWordPressPluginsV1 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_listSuggestedWordPressPluginsV1 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_listSuggestedWordPressPluginsV1. 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_listSuggestedWordPressPluginsV1 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