Deletes one or more transactions.
AI agents call transaction_delete to permanently remove resources in Money Manager MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently deletes financial transaction records. Deletion of financial data is irreversible and could result in loss of critical accounting history, tax records, or audit trails. The blast radius is high because it can delete 'one or more' transactions, potentially wiping large amounts of financial history in a single call.
From the tool's definition 'Deletes one or more transactions' — explicitly removes financial transaction records irreversibly
Documented attack patterns abuse exactly the kind of access transaction_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Money Manager MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for transaction_delete:
{
"version": "1",
"default": "deny",
"hide": [
"transaction_delete"
]
} transaction_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Deletes one or more transactions. It is categorised as a Destructive tool in the Money Manager MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Money Manager MCP Server MCP server in PolicyLayer and add a rule for transaction_delete: 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 Manager MCP Server. Nothing to install.
transaction_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the transaction_delete 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 transaction_delete. 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.
transaction_delete is provided by the Money Manager MCP Server MCP server (shahlaukik/money-manager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Money Manager 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.
18 Money Manager MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.