deleteCharge

Delete a wallet charge

SERVERGoHighLevel MCP Server SOURCEdrausal/gohighlevel-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/drausal-gohighlevel-mcp/deletecharge.md

WHAT IT DOES

What deleteCharge does on GoHighLevel MCP Server

AI agents call deleteCharge to permanently remove resources in GoHighLevel MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why deleteCharge is rated Critical

Deleting a wallet charge is an irreversible destructive action that removes financial data. While it involves financial records, the primary action is deletion/destruction rather than moving money or committing financial obligations. The blast radius is high as it permanently removes billing/payment records that may be needed for auditing or reconciliation.

From the tool's definition 'Delete a wallet charge' — permanently removes a financial record (wallet charge)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs deleteCharge safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deleteCharge, this is the rule to start with:

deleteCharge Hidden

deleteCharge is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "deleteCharge"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GoHighLevel MCP Server, apply this rule, and every deleteCharge call is checked against it from then on.

FAQ

Questions about deleteCharge

What does the deleteCharge tool do? +

Delete a wallet charge. It is categorised as a Destructive tool in the GoHighLevel MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on deleteCharge? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for deleteCharge: 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.

What risk level is deleteCharge? +

deleteCharge is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit deleteCharge? +

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

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

deleteCharge is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GoHighLevel MCP Server, and thousands of servers like it.

This server

All 406 GoHighLevel MCP Server tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →