billing_disableAutoRenewalV1

Disable auto-renewal for a subscription. Use this endpoint when disable auto-renewal for a subscription.

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 11 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/billing-disableautorenewalv1.md

WHAT IT DOES

What billing_disableAutoRenewalV1 does on Hostinger Api

AI agents use billing_disableAutoRenewalV1 to create or update resources in Hostinger Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger Api environment.

Parameter	Type	Required	Description
`subscriptionId`	string	Yes	Subscription ID

Parameters from the server's own tool schema.

RISK

Why billing_disableAutoRenewalV1 is rated Medium

This tool modifies subscription renewal settings, which is a write operation rather than read (retrieves data), execute (runs arbitrary code), or destructive (irreversible deletion). However, it affects financial/billing state and could impact subscription continuity, warranting high severity.

From the tool's definition Tool name 'billing_disableAutoRenewalV1' and description 'Disable auto-renewal for a subscription' indicate modification of subscription settings. This is a reversible write operation that changes subscription state.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

billing_disableAutoRenewalV1 Rate-limited

billing_disableAutoRenewalV1 stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "billing_disableAutoRenewalV1": {
      "limits": [
        {
          "counter": "billing_disableautorenewalv1_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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_disableAutoRenewalV1 call is checked against it from then on.

FAQ

Questions about billing_disableAutoRenewalV1

What does the billing_disableAutoRenewalV1 tool do? +

Disable auto-renewal for a subscription. Use this endpoint when disable auto-renewal for a subscription. It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does billing_disableAutoRenewalV1 accept? +

billing_disableAutoRenewalV1 accepts 1 parameter: subscriptionId. 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_disableAutoRenewalV1? +

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

billing_disableAutoRenewalV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit billing_disableAutoRenewalV1? +

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

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

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

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →