Get details of a specific expense claim including all receipts
AI agents call xero_get_expense_claim to retrieve information from Xero Expenses MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves details of an existing expense claim and its associated receipts. The use of 'get' and the retrieval-only nature (no creation, modification, deletion, or financial transaction) places it squarely in the Read category.
From the tool's definition Tool name contains 'get' and description states 'Get details of a specific expense claim' — retrieves information without modification or side effects. The phrase 'including all receipts' further confirms it queries and returns existing data.
Attacks that exploit this kind of access
Get details of a specific expense claim including all receipts. It is categorised as a Read tool in the Xero Expenses MCP MCP Server, which means it retrieves data without modifying state.
Register the Xero Expenses MCP server in PolicyLayer and add a rule for xero_get_expense_claim: 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_get_expense_claim is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the xero_get_expense_claim 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_get_expense_claim. 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_get_expense_claim 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 →