Delete an invoice from a project.
AI agents call delete_invoice to permanently remove resources in Filevine — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible delete operation on invoices, which are critical financial documents in a legal case management system. Deletion of invoices cannot be undone and could result in loss of billing records, audit trail corruption, and financial reconciliation issues. While not a direct financial transaction, it destructively removes financial artifacts that may be legally required for compliance.
From the tool's definition Tool name 'delete_invoice' combined with description 'Delete an invoice from a project' indicates irreversible removal of financial records.
Attacks that exploit this kind of access
Delete an invoice from a project. It is categorised as a Destructive tool in the Filevine MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Filevine MCP server in PolicyLayer and add a rule for delete_invoice: 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 Filevine. Nothing to install.
delete_invoice 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 delete_invoice 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_invoice. 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_invoice is provided by the Filevine MCP server (rosenadvertising/filevine-mcp). 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 →