Delete a transaction rule. Args: rule_id: The ID of the rule to delete (use get_transaction_rules to find IDs) Returns: Confirmation of deletion.
AI agents call delete_transaction_rule 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.
This tool irreversibly deletes data (a transaction rule) from the Monarch Money system. Deletion operations cannot be undone and represent the most severe category of impact. While not as critical as deleting financial records themselves, rules govern transaction processing and their deletion could disrupt automated financial workflows.
From the tool's definition Tool name contains 'delete' and description states 'Delete a transaction rule.' The function permanently removes a transaction rule without reversibility.
Documented attack patterns abuse exactly the kind of access delete_transaction_rule gives an agent:
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_rule:
{
"version": "1",
"default": "deny",
"hide": [
"delete_transaction_rule"
]
} delete_transaction_rule 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.
Delete a transaction rule. Args: rule_id: The ID of the rule to delete (use get_transaction_rules to find IDs) 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.
Register the Monarch MCP server in PolicyLayer and add a rule for delete_transaction_rule: 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.
delete_transaction_rule 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 delete_transaction_rule 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 delete_transaction_rule. 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.
delete_transaction_rule 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.
Deterministic rules across all 50 Monarch tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
50 Monarch tools catalogued and risk-classified — across an index of 42,500+ MCP servers.