wp_list_updates

List available WordPress core updates.

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-list-updates.md

WHAT IT DOES

What wp_list_updates does on Hostinger

AI agents call wp_list_updates 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_list_updates is rated Low

This tool retrieves and displays available WordPress updates as read-only data. It has no side effects, does not execute code, does not modify data, and does not trigger deployments. The primary use case is to check what updates are available before any action is taken.

From the tool's definition Tool name contains 'list' and description states 'List available WordPress core updates' — a pure query operation that retrieves update information without modifying or executing anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

wp_list_updates Allowed

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

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

FAQ

Questions about wp_list_updates

What does the wp_list_updates tool do? +

List available WordPress core updates. 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_list_updates? +

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

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

Can I rate-limit wp_list_updates? +

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

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

wp_list_updates 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

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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