Delete a payment method. DELETE /customers/{customerId}/paymentmethods/{paymentMethodId}.
AI agents call delete_customer_payment_method to permanently remove resources in Rebillia MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion operation on customer payment method records. This is destructive because once deleted, the payment method cannot be recovered without manual intervention, and it affects billing operations—any automated payments relying on that method will fail.
From the tool's definition Tool name contains 'delete' and description specifies 'Delete a payment method' with DELETE HTTP method. This irreversibly removes payment method data.
Attacks that exploit this kind of access
Delete a payment method. DELETE /customers/{customerId}/paymentmethods/{paymentMethodId}. It is categorised as a Destructive tool in the Rebillia MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Rebillia MCP Server MCP server in PolicyLayer and add a rule for delete_customer_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 Rebillia MCP Server. Nothing to install.
delete_customer_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 delete_customer_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 delete_customer_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.
delete_customer_payment_method is provided by the Rebillia MCP Server MCP server (rhinosaas/rebillia-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →