Record one purchase (or deposit) that splits across multiple categories — e.g. a receipt with both business and personal items. Creates a single balanced journal entry: one leg on the payment account (the bank/card — this is what a statement shows and what reconciliation matches) plus one leg per...
AI agents use split_transaction to create or update resources in Bookie — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bookie environment.
This tool writes new financial journal entries into the accounting system, creating records for a split transaction. While it involves financial data, it does not move real money or commit actual financial obligations — it records accounting entries in a bookkeeping system. It is reversible (a sibling delete_transaction tool exists), so Write is the appropriate category rather than Destructive or Financial.
From the tool's definition 'Creates a single balanced journal entry: one leg on the payment account...plus one leg per category' and 'Record one purchase (or deposit) that splits across multiple categories'
Attacks that exploit this kind of access
Record one purchase (or deposit) that splits across multiple categories — e.g. a receipt with both business and personal items. Creates a single balanced journal entry: one leg on the payment account (the bank/card — this is what a statement shows and what reconciliation matches) plus one leg per category. Use this instead of add_transaction when a single statement line maps to several categories. Store the full itemization on the receipt; the legs are per-category roll-ups. It is categorised as a Write tool in the Bookie MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bookie MCP server in PolicyLayer and add a rule for split_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 Bookie. Nothing to install.
split_transaction 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 split_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 split_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.
split_transaction is provided by the Bookie MCP server (yuens1002/bookie). 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 →