AI agents use create_transaction_rule to create or update resources in Monarch — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Monarch environment.
This tool creates a new transaction rule, which modifies financial application state reversibly. While the description is empty (lowering confidence slightly), the name and context of a financial management system clearly indicate a Write operation. It is not Destructive (rules can be deleted), not Financial (does not move money itself), and not Execute (does not run arbitrary code).
From the tool's definition Tool name 'create_transaction_rule' indicates creation of a transaction rule in Monarch Money financial system.
Documented attack patterns abuse exactly the kind of access create_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 create_transaction_rule:
{
"version": "1",
"default": "deny",
"tools": {
"create_transaction_rule": {
"limits": [
{
"counter": "create_transaction_rule_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_transaction_rule stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
create_transaction_rule. It is categorised as a Write tool in the Monarch MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Monarch MCP server in PolicyLayer and add a rule for create_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.
create_transaction_rule 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 create_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 create_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.
create_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.