// MCP TOOL REFERENCE

refresh_accounts

Request account data refresh from financial institutions. Args: account_ids: Specific account IDs to refresh. If omitted or empty, refreshes all active, non-hidden accounts.

ServerMonarch
CategoryExecute

How to control refresh_accounts ↓

WHAT REFRESH_ACCOUNTS ON MONARCH DOES

AI agents invoke refresh_accounts to trigger actions in Monarch. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

THE RISK

High Risk

This tool triggers an external operation — initiating a refresh/sync request to financial institutions. It doesn't merely read local data; it actively triggers a pull from external systems. It doesn't move money (not Financial), doesn't delete data (not Destructive), and isn't a simple local write.

From the tool's definition Request account data refresh from financial institutions

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

HOW TO CONTROL REFRESH_ACCOUNTS

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 refresh_accounts:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "refresh_accounts": {
      "limits": [
        {
          "counter": "refresh_accounts_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

refresh_accounts stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

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.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More Monarch tools

Destructive delete_transaction Delete a transaction from Monarch Money. Warning: This action cannot be undone. 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. 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 →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in Monarch → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-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 refresh_accounts tool do? +

Request account data refresh from financial institutions. Args: account_ids: Specific account IDs to refresh. If omitted or empty, refreshes all active, non-hidden accounts. It is categorised as a Execute tool in the Monarch MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on refresh_accounts? +

Register the Monarch MCP server in PolicyLayer and add a rule for refresh_accounts: 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 refresh_accounts? +

refresh_accounts is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit refresh_accounts? +

Yes. Add a rate_limit block to the refresh_accounts 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 refresh_accounts completely? +

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

refresh_accounts 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.

refresh_accounts

// WHAT REFRESH_ACCOUNTS ON MONARCH DOES

// THE RISK

// HOW TO CONTROL REFRESH_ACCOUNTS

// EXPLORE