Deletes an estimate by its Relay global ID. Only drafts and unsent estimates can be safely removed.
AI agents call wave_delete_estimate to permanently remove resources in Waveapps — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes estimate records from Wave Accounting. Although the qualifier 'safely removed' suggests it only applies to drafts/unsent estimates (limiting some blast radius), deletion is inherently irreversible and cannot be undone. This makes it Destructive rather than Write.
From the tool's definition Tool name contains 'delete'; description states 'Deletes an estimate' with qualifier 'safely removed', indicating irreversible removal of data.
Attacks that exploit this kind of access
Deletes an estimate by its Relay global ID. Only drafts and unsent estimates can be safely removed. It is categorised as a Destructive tool in the Waveapps MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Waveapps MCP server in PolicyLayer and add a rule for wave_delete_estimate: 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 Waveapps. Nothing to install.
wave_delete_estimate 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 wave_delete_estimate 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 wave_delete_estimate. 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.
wave_delete_estimate is provided by the Waveapps MCP server (lunaparker/waveapps-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 →