Get upcoming recurring transactions. Returns scheduled recurring transactions with their merchants, amounts, and accounts. Args: start_date: Start date in YYYY-MM-DD format (defaults to start of current month) end_date: End date in YYYY-MM-DD format (defaults to end of current month) Returns: Lis...
AI agents call get_recurring_transactions 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 retrieves and queries financial transaction data without side effects. It fits the Read category as it only fetches existing data. Severity is low because the blast radius of an AI agent querying recurring transactions is minimal—no money moves, no data is modified or deleted, and the information returned is read-only metadata about the user's own account.
From the tool's definition Tool description states 'Get upcoming recurring transactions' and 'Returns scheduled recurring transactions with their merchants, amounts, and accounts.' The parameters are date filters (start_date, end_date) for querying.
Documented attack patterns abuse exactly the kind of access get_recurring_transactions 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_recurring_transactions:
{
"version": "1",
"default": "deny",
"tools": {
"get_recurring_transactions": {}
}
}get_recurring_transactions 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 upcoming recurring transactions. Returns scheduled recurring transactions with their merchants, amounts, and accounts. Args: start_date: Start date in YYYY-MM-DD format (defaults to start of current month) end_date: End date in YYYY-MM-DD format (defaults to end of current month) Returns: List of upcoming recurring transactions. 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_recurring_transactions: 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_recurring_transactions 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_recurring_transactions 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_recurring_transactions. 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_recurring_transactions 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.