billing_setDefaultPaymentMethodV1
Set the default payment method for your account. Use this endpoint to configure the primary payment method for future orders.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/billing-setdefaultpaymentmethodv1.md
What billing_setDefaultPaymentMethodV1 does on Hostinger Api
AI agents use billing_setDefaultPaymentMethodV1 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 |
|---|---|---|---|
paymentMethodId | integer | Yes | Payment method ID |
Parameters from the server's own tool schema.
Why billing_setDefaultPaymentMethodV1 is rated Critical
This tool modifies which payment method is used for future financial transactions and orders. While it doesn't directly move money, it controls the payment instrument that will be charged for future purchases, making it a financial-category action with high severity since a misconfigured default payment method could lead to unintended charges on a wrong payment instrument.
From the tool's definition Set the default payment method for your account... configure the primary payment method for future orders
Attacks that exploit this kind of access
The rule that runs billing_setDefaultPaymentMethodV1 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_setDefaultPaymentMethodV1, this is the rule to start with:
Any call to billing_setDefaultPaymentMethodV1 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 Api, apply this rule, and every billing_setDefaultPaymentMethodV1 call is checked against it from then on.
Questions about billing_setDefaultPaymentMethodV1
Set the default payment method for your account. Use this endpoint to configure the primary payment method for future orders. 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.
billing_setDefaultPaymentMethodV1 accepts 1 parameter: paymentMethodId. Required: paymentMethodId. The full parameter table on this page comes from the server's own tool schema.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for billing_setDefaultPaymentMethodV1: 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.
billing_setDefaultPaymentMethodV1 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 billing_setDefaultPaymentMethodV1 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 billing_setDefaultPaymentMethodV1. 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.
billing_setDefaultPaymentMethodV1 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.
More on Hostinger Api, and thousands of servers like it.
Across the catalogue