New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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

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

ParameterTypeRequiredDescription
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

Questions about billing_renewSubscriptionV1

What does the billing_renewSubscriptionV1 tool do? +

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.

What parameters does billing_renewSubscriptionV1 accept? +

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.

How do I enforce a policy on billing_renewSubscriptionV1? +

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.

What risk level is billing_renewSubscriptionV1? +

billing_renewSubscriptionV1 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_renewSubscriptionV1? +

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.

How do I block billing_renewSubscriptionV1 completely? +

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.

What MCP server provides billing_renewSubscriptionV1? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hostinger Api's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.