// MCP TOOL REFERENCE

delete_transaction

Delete a transaction from Monarch Money. Warning: This action cannot be undone. Args: transaction_id: The ID of the transaction to delete Returns: Confirmation of deletion.

ServerMonarch
CategoryDestructive

How to control delete_transaction ↓

WHAT DELETE_TRANSACTION ON MONARCH DOES

AI agents call delete_transaction to permanently remove resources in Monarch — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

THE RISK

Critical Risk

This tool irreversibly deletes financial transaction records. The explicit 'cannot be undone' warning and the deletion of permanent financial data makes this Destructive rather than Write.

From the tool's definition Tool description explicitly states 'Delete a transaction from Monarch Money' and includes warning 'This action cannot be undone.' The tool name is 'delete_transaction' with a single argument 'transaction_id'.

Documented attack patterns abuse exactly the kind of access delete_transaction gives an agent:

HOW TO CONTROL DELETE_TRANSACTION

PolicyLayer is an MCP gateway — it sits between your AI agents and Monarch, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_transaction:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_transaction"
  ]
}

delete_transaction disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Monarch — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

More Monarch tools

Destructive delete_transaction_rule Delete a transaction rule. Args: rule_id: The ID of the rule to delete (use g Destructive monarch_logout Clear the stored Monarch Money session from the system keyring. Execute refresh_accounts Request account data refresh from financial institutions. Args: account_ids: Write split_transaction Split a transaction into multiple parts with different categories/merchants. The sum Write bulk_categorize_transactions bulk_categorize_transactions Write add_transaction_tag Add a tag to a transaction, preserving any tags already on it. Args: transact Write categorize_transaction Assign a category to a transaction. Args: transaction_id: The ID of the trans Write create_transaction Create a new transaction in Monarch Money. Args: date: Transaction date in YY

All 50 Monarch tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in Monarch → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the delete_transaction tool do? +

Delete a transaction from Monarch Money. Warning: This action cannot be undone. Args: transaction_id: The ID of the transaction to delete Returns: Confirmation of deletion. It is categorised as a Destructive tool in the Monarch MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_transaction? +

Register the Monarch MCP server in PolicyLayer and add a rule for delete_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 Monarch. Nothing to install.

What risk level is delete_transaction? +

delete_transaction is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_transaction? +

Yes. Add a rate_limit block to the delete_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.

How do I block delete_transaction completely? +

Set action: deny in the PolicyLayer policy for delete_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.

What MCP server provides delete_transaction? +

delete_transaction is provided by the Monarch MCP server (robcerda/monarch-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Monarch tool call.

Deterministic rules across all 50 Monarch tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN MONARCH →

Free to start. No card required.

50 Monarch tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

delete_transaction

// WHAT DELETE_TRANSACTION ON MONARCH DOES

// THE RISK

// HOW TO CONTROL DELETE_TRANSACTION

// EXPLORE