Get all available transaction categories from Monarch Money.
AI agents call get_transaction_categories to retrieve information from Monarch without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns transaction category data without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that retrieves existing categorization metadata from Monarch Money. The low severity reflects that retrieving category definitions poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name is 'get_transaction_categories' and description states 'Get all available transaction categories' — a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_transaction_categories 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 get_transaction_categories:
{
"version": "1",
"default": "deny",
"tools": {
"get_transaction_categories": {}
}
}get_transaction_categories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all available transaction categories from Monarch Money. It is categorised as a Read tool in the Monarch MCP Server, which means it retrieves data without modifying state.
Register the Monarch MCP server in PolicyLayer and add a rule for get_transaction_categories: 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.
get_transaction_categories is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_transaction_categories 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 get_transaction_categories. 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.
get_transaction_categories 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.