billing_createPurchaseOrderV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Critical RISK CLASS

Category Financial

Parameters 31 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/billing-createpurchaseorderv1.md

WHAT IT DOES

What billing_createPurchaseOrderV1 does on Hostinger Api

AI agents use billing_createPurchaseOrderV1 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
`items`	array	Yes	Catalog price items to purchase
`coupons`	array	—	Discount coupon codes
`payment_method_id`	integer	—	Payment method ID, default will be used if not provided

Parameters from the server's own tool schema.

RISK

Why billing_createPurchaseOrderV1 is rated Critical

This tool directly commits financial obligations by placing purchase orders charged to the user's payment method. Misuse could result in unauthorized purchases across any Hostinger product, making it a critical financial risk.

From the tool's definition Create a purchase order for any Hostinger product... places an order for one or more catalog items... If no payment method is provided, your default payment method will be used automatically.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

billing_createPurchaseOrderV1 Approval-gated

Any call to billing_createPurchaseOrderV1 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": {
    "billing_createPurchaseOrderV1": {
      "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 billing_createPurchaseOrderV1 call is checked against it from then on.

FAQ

Questions about billing_createPurchaseOrderV1

What does the billing_createPurchaseOrderV1 tool do? +

Create a purchase order for any Hostinger product. This unified endpoint places an order for one or more catalog items and works across all Hostinger products, leveraging the existing billing infrastructure. Use the [catalog endpoint](#tag/billing-catalog) to look up the item_id values available for purchase. If no payment method is provided, your default payment method will be used automatically. This endpoint only places the order. Product-specific provisioning (e.g. VPS setup or domain registration) is not performed here — once the order completes, use the relevant product endpoints or [hPanel](https://hpanel.hostinger.com/) to finalize setup. Use this endpoint to purchase any product available in the catalog. 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 billing_createPurchaseOrderV1 accept? +

billing_createPurchaseOrderV1 accepts 3 parameters: items, coupons, payment_method_id. Required: items. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on billing_createPurchaseOrderV1? +

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

billing_createPurchaseOrderV1 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 billing_createPurchaseOrderV1? +

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

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

billing_createPurchaseOrderV1 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 382 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 →