Retrieves any spent or received money transactions
AI agents call list_bank_transactions to retrieve information from Xero MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical transaction data from the accounting system without creating, modifying, or deleting records. While it accesses financial information, the operation itself is read-only with no side effects. The risk is low because viewing past transactions does not alter financial state or create obligations.
From the tool's definition Tool name 'list_bank_transactions' and description 'Retrieves any spent or received money transactions' indicate a retrieval operation with no modification capability.
Documented attack patterns abuse exactly the kind of access list_bank_transactions 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 list_bank_transactions:
{
"version": "1",
"default": "deny",
"tools": {
"list_bank_transactions": {}
}
} list_bank_transactions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieves any spent or received money transactions. It is categorised as a Read tool in the Xero MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Xero MCP Server MCP server in PolicyLayer and add a rule for list_bank_transactions: 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.
list_bank_transactions 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 list_bank_transactions 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 list_bank_transactions. 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.
list_bank_transactions 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.