hosting_updateWordPressCoreV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 42 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What hosting_updateWordPressCoreV1 does on Hostinger Api

AI agents use hosting_updateWordPressCoreV1 to create or update resources in Hostinger Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger Api environment.

Parameter	Type	Required	Description
`minor`	boolean	—	Update the minor version only.
`version`	string	—	Update to a specific WordPress core version.
`software`	string	Yes	WordPress installation (software) identifier
`username`	string	Yes	username parameter

Parameters from the server's own tool schema.

RISK

Why hosting_updateWordPressCoreV1 is rated Medium

This tool updates WordPress core software, which is a reversible write/modification operation. While it changes the software version, it doesn't irreversibly delete data. It could cause issues if a bad version is applied, but updates can generally be rolled back. The async nature means it queues a job rather than executing immediately. Severity is medium because a bad update could break a production website.

From the tool's definition Update the WordPress core for the specified installation (minor update or a specific version)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

hosting_updateWordPressCoreV1 Rate-limited

hosting_updateWordPressCoreV1 stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hosting_updateWordPressCoreV1": {
      "limits": [
        {
          "counter": "hosting_updatewordpresscorev1_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about hosting_updateWordPressCoreV1

What does the hosting_updateWordPressCoreV1 tool do? +

Update the WordPress core for the specified installation (minor update or a specific version). Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the id field). This operation is asynchronous: a successful response only means the update job has been queued. It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does hosting_updateWordPressCoreV1 accept? +

hosting_updateWordPressCoreV1 accepts 4 parameters: minor, version, 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_updateWordPressCoreV1? +

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

hosting_updateWordPressCoreV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit hosting_updateWordPressCoreV1? +

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

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

hosting_updateWordPressCoreV1 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

Govern customer-ops agents →Argument validation →Scoped token →