Retrieves a single spent or received money transaction by its Xero bank transaction ID
AI agents call get_bank_transaction 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 queries and returns data about a bank transaction without creating, modifying, deleting, or executing any side effects. It is a straightforward read operation that retrieves financial information from Xero's accounting system. While the data returned is financial in nature, the tool itself performs no financial action (no movement of money, no obligations created).
From the tool's definition 'Retrieves a single spent or received money transaction by its Xero bank transaction ID' — the verb 'retrieves' and the read-only nature of querying an existing transaction indicates no modification, deletion, or execution of external actions.
Documented attack patterns abuse exactly the kind of access get_bank_transaction 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 get_bank_transaction:
{
"version": "1",
"default": "deny",
"tools": {
"get_bank_transaction": {}
}
} get_bank_transaction 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 a single spent or received money transaction by its Xero bank transaction ID. 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 get_bank_transaction: 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.
get_bank_transaction 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 get_bank_transaction 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 get_bank_transaction. 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.
get_bank_transaction 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.