Create a spend money transaction (direct expense) in Xero - use for already-paid expenses like receipts
AI agents use xero_create_expense 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 financial transaction records (expenses) in Xero accounting software, which is a reversible write operation. While it involves financial systems, it does not move money directly (Financial category requires active payment/transfer execution) nor does it permanently delete data (Destructive).
From the tool's definition Tool name 'xero_create_expense' and description 'Create a spend money transaction (direct expense) in Xero' indicate creation of financial records.
Attacks that exploit this kind of access
Create a spend money transaction (direct expense) in Xero - use for already-paid expenses like receipts. 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_expense: 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_expense 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_expense 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_expense. 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_expense 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 →