This record as markdown: /tools/hostinger-mcp/vps-purchase.md
What vps_purchase does on Hostinger
AI agents use vps_purchase to commit financial operations through Hostinger, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why vps_purchase is rated Critical
Purchasing a VPS directly involves a financial commitment (billing/payment). This falls squarely in the Financial category, which is the most severe. Misuse by an AI agent could result in unauthorized charges or subscription commitments, warranting a critical severity rating.
From the tool's definition "Purchase a new virtual machine" — this tool initiates a financial transaction to acquire a VPS product, committing monetary obligations.
Attacks that exploit this kind of access
The rule that runs vps_purchase 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 vps_purchase, this is the rule to start with:
Any call to vps_purchase is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger, apply this rule, and every vps_purchase call is checked against it from then on.
Questions about vps_purchase
Purchase a new virtual machine. It is categorised as a Financial tool in the Hostinger MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Hostinger MCP server in PolicyLayer and add a rule for vps_purchase: 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.
vps_purchase is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the vps_purchase 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 vps_purchase. 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.
vps_purchase 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.
Across the catalogue