billing_deletePaymentMethodV1
Delete a payment method from your account. Use this endpoint to remove unused payment methods from user accounts.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/billing-deletepaymentmethodv1.md
What billing_deletePaymentMethodV1 does on Hostinger Api
AI agents call billing_deletePaymentMethodV1 to permanently remove resources in Hostinger Api, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
paymentMethodId | integer | Yes | Payment method ID |
Parameters from the server's own tool schema.
Why billing_deletePaymentMethodV1 is rated Critical
Deleting a payment method is a destructive action that irreversibly removes financial account information. While not a direct financial transaction, it permanently modifies critical account configuration and could disrupt billing operations if the wrong method is deleted. This ranks above Write/Execute due to its irreversibility and potential impact on account functionality.
From the tool's definition Tool name explicitly contains 'delete' (billing_deletePaymentMethodV1) and description states 'Delete a payment method from your account' and 'remove unused payment methods from user accounts.' This is an irreversible removal operation.
Attacks that exploit this kind of access
The rule that runs billing_deletePaymentMethodV1 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_deletePaymentMethodV1, this is the rule to start with:
billing_deletePaymentMethodV1 is removed from the agent's tool list entirely, so the agent never calls 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_deletePaymentMethodV1 call is checked against it from then on.
Questions about billing_deletePaymentMethodV1
Delete a payment method from your account. Use this endpoint to remove unused payment methods from user accounts. It is categorised as a Destructive tool in the Hostinger Api MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
billing_deletePaymentMethodV1 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_deletePaymentMethodV1: 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_deletePaymentMethodV1 is a Destructive 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_deletePaymentMethodV1 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_deletePaymentMethodV1. 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_deletePaymentMethodV1 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