Updates an existing sales invoice or purchase bill (typically a draft) to change fields like line items and account codes
AI agents use update_invoice to create or update resources in Xero MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xero MCP Server environment.
The tool creates or modifies financial data (invoices/bills) in Xero accounting software. While it operates on financial records, it does not directly move money or commit financial obligations—those are the characteristics of Financial category. The action is reversible (invoices can be further updated or reverted), making it Write rather than Destructive.
From the tool's definition Tool performs 'Updates an existing sales invoice or purchase bill' with ability to 'change fields like line items and account codes'. This modifies financial records reversibly.
Documented attack patterns abuse exactly the kind of access update_invoice gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Xero MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_invoice:
{
"version": "1",
"default": "deny",
"tools": {
"update_invoice": {
"limits": [
{
"counter": "update_invoice_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} update_invoice stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Updates an existing sales invoice or purchase bill (typically a draft) to change fields like line items and account codes. It is categorised as a Write tool in the Xero MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Xero MCP Server MCP server in PolicyLayer and add a rule for update_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 MCP Server. Nothing to install.
update_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 update_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 update_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.
update_invoice is provided by the Xero MCP Server MCP server (john-zhang-dev/xero-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Xero MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 Xero MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.