This record as markdown: /tools/hostinger-mcp/billing-delete-payment-method.md
What billing_delete_payment_method does on Hostinger
AI agents call billing_delete_payment_method to permanently remove resources in Hostinger, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why billing_delete_payment_method is rated Critical
Deleting a payment method is an irreversible destructive action. While not directly moving funds, it removes financial infrastructure and cannot be undone without re-entry. The blast radius is high: an AI agent could maliciously or mistakenly remove legitimate payment methods, disrupting billing operations, service continuity, or customer accounts.
From the tool's definition Tool name: 'billing_delete_payment_method' — 'delete' indicates irreversible removal. Description: 'Delete a payment method' — explicit deletion of billing data.
Attacks that exploit this kind of access
The rule that runs billing_delete_payment_method safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For billing_delete_payment_method, this is the rule to start with:
billing_delete_payment_method 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, apply this rule, and every billing_delete_payment_method call is checked against it from then on.
Questions about billing_delete_payment_method
Delete a payment method. It is categorised as a Destructive tool in the Hostinger MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hostinger MCP server in PolicyLayer and add a rule for billing_delete_payment_method: 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. Nothing to install.
billing_delete_payment_method 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_delete_payment_method 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_delete_payment_method. 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_delete_payment_method is provided by the Hostinger MCP server (idugeni/hostinger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger, and thousands of servers like it.
Across the catalogue