Change the category account on an existing journal entry — useful for fixing an imported entry posted to the wrong account, or for categorizing an entry that was added without one. Works on entries with exactly one income/expense leg; for split entries (multiple category legs), delete and re-ente...
AI agents use categorize_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 modifies an existing journal entry by updating its category account. It is a reversible modification (the entry can be re-categorized or deleted and re-entered), placing it in the Write category. Misuse could lead to incorrect financial records but does not directly move money or irreversibly destroy data, so severity is medium.
From the tool's definition Change the category account on an existing journal entry — useful for fixing an imported entry posted to the wrong account, or for categorizing an entry that was added without one.
Attacks that exploit this kind of access
Change the category account on an existing journal entry — useful for fixing an imported entry posted to the wrong account, or for categorizing an entry that was added without one. Works on entries with exactly one income/expense leg; for split entries (multiple category legs), delete and re-enter with split_transaction. Supply either targetAccountId (explicit) or ruleId (apply a stored categorize rule). Also accepts propertyId / clearProperty to update the entry. 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 categorize_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.
categorize_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 categorize_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 categorize_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.
categorize_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 →