This record as markdown: /tools/hostinger-mcp/wp-get-version.md
What wp_get_version does on Hostinger
AI agents call wp_get_version 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.
Why wp_get_version is rated Low
This tool retrieves metadata about an installed WordPress instance (its core version). It is a passive read operation with no side effects, no destructive capability, and no financial impact. The low severity reflects minimal blast radius if misused—an AI agent calling this repeatedly would only gather informational data.
From the tool's definition Tool name 'wp_get_version' and description 'Show WordPress core version' indicate a query operation that retrieves version information without modifying data or triggering external actions.
Attacks that exploit this kind of access
The rule that runs wp_get_version 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_get_version, this is the rule to start with:
wp_get_version is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger, apply this rule, and every wp_get_version call is checked against it from then on.
Questions about wp_get_version
Show WordPress core version. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.
Register the Hostinger MCP server in PolicyLayer and add a rule for wp_get_version: 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.
wp_get_version is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the wp_get_version 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.
Set action: deny in the PolicyLayer policy for wp_get_version. 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.
wp_get_version 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.
More on Hostinger, and thousands of servers like it.
This server
Across the catalogue