domains_purchaseNewDomainV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Critical RISK CLASS

Category Financial

Parameters 62 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/domains-purchasenewdomainv1.md

WHAT IT DOES

What domains_purchaseNewDomainV1 does on Hostinger Api

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

Parameter	Type	Required	Description
`domain`	string	Yes	Domain name
`coupons`	array	—	Discount coupon codes
`item_id`	string	Yes	Catalog price item ID
`domain_contacts`	object	—	Domain contact information
`payment_method_id`	integer	—	Payment method ID, default will be used if not provided
`additional_details`	object	—	Additional registration data, possible values depends on TLD

Parameters from the server's own tool schema.

RISK

Why domains_purchaseNewDomainV1 is rated Critical

This tool directly initiates a financial transaction — purchasing and registering a domain — which charges the user's payment method. It commits a real monetary obligation and is irreversible once processed, placing it firmly in the Financial category, which is the most severe applicable category.

From the tool's definition Purchase and register a new domain name... your default payment method will be used automatically

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

domains_purchaseNewDomainV1 Approval-gated

Any call to domains_purchaseNewDomainV1 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_purchaseNewDomainV1": {
      "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 Api, apply this rule, and every domains_purchaseNewDomainV1 call is checked against it from then on.

FAQ

Questions about domains_purchaseNewDomainV1

What does the domains_purchaseNewDomainV1 tool do? +

Purchase and register a new domain name. If registration fails, login to [hPanel](https://hpanel.hostinger.com/) and check domain registration status. If no payment method is provided, your default payment method will be used automatically. If no WHOIS information is provided, default contact information for that TLD will be used. Before making request, ensure WHOIS information for desired TLD exists in your account. Some TLDs require additional_details to be provided and these will be validated before completing purchase. Use this endpoint to register new domains for users. It is categorised as a Financial tool in the Hostinger Api MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does domains_purchaseNewDomainV1 accept? +

domains_purchaseNewDomainV1 accepts 6 parameters: domain, coupons, item_id, domain_contacts, payment_method_id, additional_details. Required: domain, item_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on domains_purchaseNewDomainV1? +

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

domains_purchaseNewDomainV1 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_purchaseNewDomainV1? +

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

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

domains_purchaseNewDomainV1 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 → 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 →