hosting_deleteWordPressInstallationV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Critical RISK CLASS

Category Destructive

Parameters 22 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What hosting_deleteWordPressInstallationV1 does on Hostinger Api

AI agents call hosting_deleteWordPressInstallationV1 to permanently remove resources in Hostinger Api, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required	Description
`software`	string	Yes	WordPress installation (software) identifier
`username`	string	Yes	username parameter

Parameters from the server's own tool schema.

RISK

Why hosting_deleteWordPressInstallationV1 is rated Critical

This tool irreversibly deletes an entire WordPress installation and all its associated data (plugins, themes, staging sites, database). Once executed, the deletion cannot be undone. The blast radius is critical because an AI agent could destroy a customer's entire website and data with a single call.

From the tool's definition Delete the specified WordPress installation, with optional file and database removal. This removes all associated components including plugins, themes, staging websites and any other related data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

hosting_deleteWordPressInstallationV1 Hidden

hosting_deleteWordPressInstallationV1 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "hosting_deleteWordPressInstallationV1"
  ]
}

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

FAQ

Questions about hosting_deleteWordPressInstallationV1

What does the hosting_deleteWordPressInstallationV1 tool do? +

Delete the specified WordPress installation, with optional file and database removal. This removes all associated components including plugins, themes, staging websites and any other related data. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the id field). It is categorised as a Destructive tool in the Hostinger Api MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does hosting_deleteWordPressInstallationV1 accept? +

hosting_deleteWordPressInstallationV1 accepts 2 parameters: software, username. Required: software, username. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hosting_deleteWordPressInstallationV1? +

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

hosting_deleteWordPressInstallationV1 is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit hosting_deleteWordPressInstallationV1? +

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

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

hosting_deleteWordPressInstallationV1 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 → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →