Delete a wallet charge by charge ID. This removes/refunds the specified charge.
AI agents use delete_billing_charge to commit financial operations through GoHighLevel MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool performs a financial operation by removing or refunding a billing charge. It is both financial (refund/reversal of a charge) and potentially destructive (deletion of billing record). Financial is the most severe applicable category. Misuse could result in unauthorized refunds or financial record manipulation, making it critical severity.
From the tool's definition Delete a wallet charge by charge ID. This removes/refunds the specified charge.
Documented attack patterns abuse exactly the kind of access delete_billing_charge gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_billing_charge:
{
"version": "1",
"default": "deny",
"tools": {
"delete_billing_charge": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to delete_billing_charge is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Delete a wallet charge by charge ID. This removes/refunds the specified charge. It is categorised as a Financial tool in the GoHighLevel MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for delete_billing_charge: 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 GoHighLevel MCP Server. Nothing to install.
delete_billing_charge is a Financial 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_billing_charge 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_billing_charge. 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_billing_charge is provided by the GoHighLevel MCP Server MCP server (busybee3333/go-high-level-mcp-2026-complete). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 566 GoHighLevel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
566 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.