This record as markdown: /tools/aiwerk-mcp-server-ghl/marketplace-delete-charge.md
What marketplace_delete_charge does on Ghl
AI agents use marketplace_delete_charge to commit financial operations through Ghl, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
chargeId | string | Yes | ID of the charge to delete |
Parameters from the server's own tool schema.
Why marketplace_delete_charge is rated Critical
marketplace_delete_charge moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Attacks that exploit this kind of access
The rule that runs marketplace_delete_charge safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For marketplace_delete_charge, this is the rule to start with:
Any call to marketplace_delete_charge is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every marketplace_delete_charge call is checked against it from then on.
Questions about marketplace_delete_charge
Delete a wallet charge. It is categorised as a Financial tool in the Ghl MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
marketplace_delete_charge accepts 1 parameter: chargeId. Required: chargeId. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for marketplace_delete_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 Ghl. Nothing to install.
marketplace_delete_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 marketplace_delete_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 marketplace_delete_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.
marketplace_delete_charge is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
Across the catalogue