Creates one or more spent or received money transaction. Only use this tool when user has directly and explicitly ask you to create transactions.
AI agents use create_bank_transactions to create or update resources in Xero MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xero MCP Server environment.
This tool creates financial transactions (spent or received money) in Xero accounting software. While it records financial data rather than directly moving money, creating bank transactions has significant financial record-keeping implications and could misrepresent financial state if misused.
From the tool's definition Creates one or more spent or received money transaction
Documented attack patterns abuse exactly the kind of access create_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 create_bank_transactions:
{
"version": "1",
"default": "deny",
"tools": {
"create_bank_transactions": {
"limits": [
{
"counter": "create_bank_transactions_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_bank_transactions stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Creates one or more spent or received money transaction. Only use this tool when user has directly and explicitly ask you to create transactions. It is categorised as a Write tool in the Xero MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Xero MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_bank_transactions 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 create_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 create_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.
create_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.