billing_renewSubscriptionV1
Create a renewal order for an existing Hostinger subscription. This endpoint places a renewal order for a single subscription, leveraging the existing billing infrastructure. Use the [subscriptions endpoint](#tag/billing-subscriptions) to look up the subscriptionId values available for renewal. I...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/billing-renewsubscriptionv1.md
What billing_renewSubscriptionV1 does on Hostinger Api
AI agents use billing_renewSubscriptionV1 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 |
|---|---|---|---|
coupons | array | — | Discount coupon codes |
subscriptionId | string | Yes | Subscription ID |
payment_method_id | integer | — | Payment method ID, default will be used if not provided |
Parameters from the server's own tool schema.
Why billing_renewSubscriptionV1 is rated Critical
This tool creates a financial transaction by placing a renewal order for a subscription, which charges the user's payment method. This directly commits a financial obligation and involves billing/payment processing, making it a Financial category tool with critical severity due to the potential for unauthorized charges.
From the tool's definition Create a renewal order for an existing Hostinger subscription... places a renewal order for a single subscription, leveraging the existing billing infrastructure... default payment method will be used automatically
Attacks that exploit this kind of access
The rule that runs billing_renewSubscriptionV1 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_renewSubscriptionV1, this is the rule to start with:
Any call to billing_renewSubscriptionV1 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_renewSubscriptionV1 call is checked against it from then on.
Questions about billing_renewSubscriptionV1
Create a renewal order for an existing Hostinger subscription. This endpoint places a renewal order for a single subscription, leveraging the existing billing infrastructure. Use the [subscriptions endpoint](#tag/billing-subscriptions) to look up the subscriptionId values available for renewal. If no payment method is provided, your default payment method will be used automatically. Use this endpoint to renew any subscription available in your account. 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_renewSubscriptionV1 accepts 3 parameters: coupons, subscriptionId, payment_method_id. Required: subscriptionId. 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_renewSubscriptionV1: 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_renewSubscriptionV1 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_renewSubscriptionV1 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_renewSubscriptionV1. 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_renewSubscriptionV1 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