hosting_listWordPressInstallationsV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Low RISK CLASS

Category Read

Parameters 30 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-listwordpressinstallationsv1.md

WHAT IT DOES

What hosting_listWordPressInstallationsV1 does on Hostinger Api

AI agents call hosting_listWordPressInstallationsV1 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
`domain`	string	—	Filter by domain name (exact match)
`username`	string	—	Filter by specific username
`ownership`	string	—	Filter by ownership type. Defaults to "owned". Use "all" to include both owned and managed installations.

Parameters from the server's own tool schema.

RISK

Why hosting_listWordPressInstallationsV1 is rated Low

This tool retrieves and lists existing WordPress installation data. It performs no modifications, deletions, or external operations—it only queries and returns information to the caller. The mention of filtering by username and domain confirms it is a retrieval mechanism.

From the tool's definition The tool 'List WordPress installations' with description stating 'List WordPress installations accessible to the authenticated client' and 'to discover existing WordPress installations' indicates a query/retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hosting_listWordPressInstallationsV1 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_listWordPressInstallationsV1, this is the rule to start with:

hosting_listWordPressInstallationsV1 Allowed

hosting_listWordPressInstallationsV1 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": {
    "hosting_listWordPressInstallationsV1": {}
  }
}

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

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

FAQ

Questions about hosting_listWordPressInstallationsV1

What does the hosting_listWordPressInstallationsV1 tool do? +

List WordPress installations accessible to the authenticated client. Use this endpoint to discover existing WordPress installations and to poll for installation status after calling the install endpoint. When a newly requested installation appears in this list, WordPress is ready. Filter by username and domain to narrow results to a specific website. Each installation includes a valid flag and, when invalid, a validationError describing why. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.

What parameters does hosting_listWordPressInstallationsV1 accept? +

hosting_listWordPressInstallationsV1 accepts 3 parameters: domain, username, ownership. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hosting_listWordPressInstallationsV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for hosting_listWordPressInstallationsV1: 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.

What risk level is hosting_listWordPressInstallationsV1? +

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

Can I rate-limit hosting_listWordPressInstallationsV1? +

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

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

hosting_listWordPressInstallationsV1 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.

KEEP EXPLORING

More on Hostinger Api, and thousands of servers like it.

This server

All 258 Hostinger Api tools →

Across the catalogue

The MCP Attack Database →

Guides

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