domains_purchase

Purchase a new domain.

SERVERHostinger SOURCEidugeni/hostinger-mcp

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hostinger-mcp/domains-purchase.md

WHAT IT DOES

What domains_purchase does on Hostinger

AI agents use domains_purchase to commit financial operations through Hostinger, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why domains_purchase is rated Critical

Purchasing a domain involves a real monetary charge to the account. This is a financial commitment that cannot be trivially reversed and may result in immediate billing. Financial is the highest severity category and clearly applies here.

From the tool's definition "Purchase a new domain" — explicitly commits a financial transaction to acquire a domain registration.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

domains_purchase Approval-gated

Any call to domains_purchase is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "domains_purchase": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger, apply this rule, and every domains_purchase call is checked against it from then on.

FAQ

Questions about domains_purchase

What does the domains_purchase tool do? +

Purchase a new domain. 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.

How do I enforce a policy on domains_purchase? +

Register the Hostinger MCP server in PolicyLayer and add a rule for domains_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.

What risk level is domains_purchase? +

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

Can I rate-limit domains_purchase? +

Yes. Add a rate_limit block to the domains_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.

How do I block domains_purchase completely? +

Set action: deny in the PolicyLayer policy for domains_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.

What MCP server provides domains_purchase? +

domains_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.

KEEP EXPLORING

More on Hostinger, and thousands of servers like it.

This server

All 284 Hostinger tools → Critical-risk tools on this server →

Across the catalogue

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

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →