fin_deletar_bill
Hard-delete de uma bill recorrente. Só funciona se NENHUMA ocorrência foi paga. QUANDO USAR: remover bill criada por engano (nome/categoria errada) antes de qualquer pagamento. NÃO USAR QUANDO: a bill já tem ocorrências pagas — use fin_editar_bill com is_active: false (soft-delete, preserva histó...
This record as markdown: /tools/genius-fin-mcp/fin-deletar-bill.md
What fin_deletar_bill does on Genius Fin
AI agents call fin_deletar_bill to permanently remove resources in Genius Fin, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why fin_deletar_bill is rated Critical
An AI agent that decides to call fin_deletar_bill doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Genius Fin is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs fin_deletar_bill safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genius Fin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fin_deletar_bill, this is the rule to start with:
fin_deletar_bill is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Genius Fin, apply this rule, and every fin_deletar_bill call is checked against it from then on.
Questions about fin_deletar_bill
Hard-delete de uma bill recorrente. Só funciona se NENHUMA ocorrência foi paga. QUANDO USAR: remover bill criada por engano (nome/categoria errada) antes de qualquer pagamento. NÃO USAR QUANDO: a bill já tem ocorrências pagas — use fin_editar_bill com is_active: false (soft-delete, preserva histórico). CAMPOS: - bill_id: string UUID (obrigatório). REGRAS DE NEGÓCIO: - Se a bill tem ≥1 ocorrência com transaction_id != null, retorna 409 com soft_delete_hint. - Ocorrências NÃO pagas são deletadas em cascata (FK ON DELETE CASCADE). It is categorised as a Destructive tool in the Genius Fin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Genius Fin MCP server in PolicyLayer and add a rule for fin_deletar_bill: 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 Genius Fin. Nothing to install.
fin_deletar_bill 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 fin_deletar_bill 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 fin_deletar_bill. 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.
fin_deletar_bill is provided by the Genius Fin MCP server (genius-fin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genius Fin, and thousands of servers like it.
Across the catalogue