Remove uma cobrança via DELETE /api/v1/charge/{id}.
AI agents call woovi_delete_charge to permanently remove resources in Payments MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently deletes a payment charge via a DELETE API call. This is irreversible — once a charge is removed, it cannot be recovered. Misuse could result in loss of payment records, failed collections, or financial reconciliation issues, making it a Destructive action with high severity.
From the tool's definition 'woovi_delete_charge' and 'Remove uma cobrança via DELETE /api/v1/charge/{id}' — explicitly uses HTTP DELETE to remove a charge, which is an irreversible deletion operation.
Attacks that exploit this kind of access
Remove uma cobrança via DELETE /api/v1/charge/{id}. It is categorised as a Destructive tool in the Payments MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Payments MCP server in PolicyLayer and add a rule for woovi_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 Payments MCP. Nothing to install.
woovi_delete_charge 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 woovi_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 woovi_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.
woovi_delete_charge is provided by the Payments MCP server (lpillonwp/mcp-payments). 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 →