Update a DRAFT sales invoice as one consolidated invoice with one line item
AI agents use xero_update_draft_invoice to create or update resources in Xero Expenses MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xero Expenses MCP environment.
This tool creates or modifies financial data (invoices) in a reversible manner. While it affects financial documents, the action is not irreversible (invoices in draft state can be further modified or deleted), and it doesn't move money or commit financial obligations.
From the tool's definition Tool name contains 'update' and description states 'Update a DRAFT sales invoice'. The operation modifies an existing invoice document by consolidating it into a single line item.
Attacks that exploit this kind of access
Update a DRAFT sales invoice as one consolidated invoice with one line item. It is categorised as a Write tool in the Xero Expenses MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Xero Expenses MCP server in PolicyLayer and add a rule for xero_update_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_update_draft_invoice is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the xero_update_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_update_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_update_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 →