wp_detect_installations

Auto-detect WordPress installations on a hosting account.

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-detect-installations.md

WHAT IT DOES

What wp_detect_installations does on Hostinger

AI agents call wp_detect_installations 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_detect_installations is rated Low

This tool performs detection and enumeration of WordPress installations—a read-only operation that retrieves information about what WordPress sites exist on an account. It has no side effects, does not modify data, execute arbitrary operations, or delete anything. The 'detect' and 'list' semantics align with the Read category.

From the tool's definition Tool name 'wp_detect_installations' and description 'Auto-detect WordPress installations on a hosting account' indicate passive discovery/querying of existing WordPress instances with no modification or execution of code.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

wp_detect_installations Allowed

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

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_detect_installations call is checked against it from then on.

FAQ

Questions about wp_detect_installations

What does the wp_detect_installations tool do? +

Auto-detect WordPress installations on a hosting account. 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_detect_installations? +

Register the Hostinger MCP server in PolicyLayer and add a rule for wp_detect_installations: 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_detect_installations? +

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

Can I rate-limit wp_detect_installations? +

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

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

wp_detect_installations 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

detect_slop on Slop Cop → The MCP Attack Database →

Guides

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