Update an existing transaction. The API requires the full transaction payload on every edit, so you must supply walletId, categoryId, amount, and date (fetch the transaction with get_transactions first if you need the current values). categoryId should be the global category ID from get_all_categ...
AI agents use edit_transaction to create or update resources in Money Lover MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Money Lover MCP Server environment.
This tool creates reversible modifications to financial transaction records. While it modifies financial data, it does not move money, create financial obligations, or delete records irreversibly—those would be Financial or Destructive categories respectively.
From the tool's definition The tool "edit_transaction" updates an existing transaction by modifying its properties (walletId, categoryId, amount, date).
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Update an existing transaction. The API requires the full transaction payload on every edit, so you must supply walletId, categoryId, amount, and date (fetch the transaction with get_transactions first if you need the current values). categoryId should be the global category ID from get_all_categories or from an existing transaction response. It is categorised as a Write tool in the Money Lover MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Money Lover MCP Server MCP server in PolicyLayer and add a rule for edit_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 Money Lover MCP Server. Nothing to install.
edit_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 edit_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 edit_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.
edit_transaction is provided by the Money Lover MCP Server MCP server (juansebashr/moneylover-mcp). 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 →