Delete a DRAFT sales invoice in Xero
AI agents call xero_delete_draft_invoice to permanently remove resources in Xero Expenses MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a draft invoice from Xero, which cannot be undone. Even though it operates only on draft invoices (limiting scope), deletion is inherently a destructive action. The tool directly modifies financial records in an accounting system, making misuse by an AI agent a significant risk—invoices could be erased without authorization, disrupting accounting workflows and audit trails.
From the tool's definition Tool name explicitly states 'delete' and description confirms it 'Delete a DRAFT sales invoice in Xero'. Deletion is irreversible data destruction.
Attacks that exploit this kind of access
Delete a DRAFT sales invoice in Xero. It is categorised as a Destructive tool in the Xero Expenses MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Xero Expenses MCP server in PolicyLayer and add a rule for xero_delete_draft_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 Xero Expenses MCP. Nothing to install.
xero_delete_draft_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 xero_delete_draft_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 xero_delete_draft_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.
xero_delete_draft_invoice is provided by the Xero Expenses MCP server (muness/xero-expenses-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 →