hosting_detectWordPressInstallationsV1
Trigger a background scan to detect WordPress installations for the account. This operation is asynchronous: a successful response only means the scan has been queued. Poll GET /api/hosting/v1/wordpress/installations to fetch the detected installations once the scan completes.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-detectwordpressinstallationsv1.md
What hosting_detectWordPressInstallationsV1 does on Hostinger Api
AI agents invoke hosting_detectWordPressInstallationsV1 to trigger actions in Hostinger Api. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
username | string | Yes | username parameter |
Parameters from the server's own tool schema.
Why hosting_detectWordPressInstallationsV1 is rated High
The tool triggers an external background operation (a scan) on the hosting infrastructure. It doesn't read, write, or destroy data directly — it initiates an asynchronous process. This fits the Execute category as it triggers an external operation. The blast radius is low since it's a read-only scan with no destructive or financial implications.
From the tool's definition Trigger a background scan to detect WordPress installations for the account. This operation is asynchronous: a successful response only means the scan has been queued.
Attacks that exploit this kind of access
The rule that runs hosting_detectWordPressInstallationsV1 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_detectWordPressInstallationsV1, this is the rule to start with:
hosting_detectWordPressInstallationsV1 stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_detectWordPressInstallationsV1 call is checked against it from then on.
Questions about hosting_detectWordPressInstallationsV1
Trigger a background scan to detect WordPress installations for the account. This operation is asynchronous: a successful response only means the scan has been queued. Poll GET /api/hosting/v1/wordpress/installations to fetch the detected installations once the scan completes. It is categorised as a Execute tool in the Hostinger Api MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
hosting_detectWordPressInstallationsV1 accepts 1 parameter: username. Required: username. 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_detectWordPressInstallationsV1: 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_detectWordPressInstallationsV1 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the hosting_detectWordPressInstallationsV1 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_detectWordPressInstallationsV1. 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_detectWordPressInstallationsV1 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.
Across the catalogue