Create a receipt WITHOUT submitting as expense claim - use this to batch multiple receipts into one claim later
AI agents use xero_create_receipt 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 a receipt record in Xero accounting software. Creation of financial records is a reversible Write operation (receipts can be deleted or edited). It does not delete data (not Destructive), does not move money directly (not Financial — it only records a receipt, not a transaction), and does not execute arbitrary code (not Execute).
From the tool's definition Tool description states 'Create a receipt' — a write operation that modifies accounting data. The server description confirms tools 'create and manage invoices, bills, expenses, and expense claims,' placing this in the Write category.
Attacks that exploit this kind of access
Create a receipt WITHOUT submitting as expense claim - use this to batch multiple receipts into one claim later. 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_create_receipt: 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_create_receipt 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_create_receipt 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_create_receipt. 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_create_receipt 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 →