// SCAN REPORT

Firefly III MCP Server

23 tools. 15 can modify or destroy data without limits.

6 destructive tools with no built-in limits. Policy required.

Last updated: 3 Jul 2026

15 can modify or destroy data

8 read-only

23 tools total

Community server · catalogue entry verified 03/07/2026

How to control Firefly III MCP Server ↓

TOOL MAP

What Firefly III MCP Server exposes to your agents

Read (8) Write / Execute (9) Destructive / Financial (6)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Firefly III MCP Server tools

Financial · High firefly_create_transaction This tool creates financial transactions including withdrawals, deposits, and transfers — directly committing financial record entries that affect account balances. Destructive · Critical firefly_delete_account This tool irreversibly deletes financial account records and all associated transaction data with no recovery mechanism. Destructive · High firefly_delete_budget This tool permanently removes financial data (a budget) from the system. Destructive · High firefly_delete_category This tool irreversibly removes a category from the financial system and severs its associations with existing transactions.

15 of Firefly III MCP Server's 23 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Firefly III MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Firefly III MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default

{
  "firefly_create_transaction": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Deny destructive operations

{
  "firefly_delete_account": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "firefly_create_account": {
    "limits": [
      {
        "counter": "firefly_create_account_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "firefly_get_account": {
    "limits": [
      {
        "counter": "firefly_get_account_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Firefly III MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON FIREFLY III →

Instant setup, no code required.

FULL CATALOGUE

All 23 Firefly III MCP Server tools

FINANCIAL 1 tools

Financial firefly_create_transaction Create a new transaction in Firefly III. Supports withdrawals (expenses), deposits (income), and transfers be

DESTRUCTIVE 5 tools

Destructive firefly_delete_account Permanently delete an account. All linked transactions will also be deleted. This cannot be undone. Destructive firefly_delete_budget Delete a budget. Transactions linked to this budget will have their budget cleared. Destructive firefly_delete_category Delete a category. Transactions using this category will have their category cleared. Destructive firefly_delete_tag Delete a tag. It will be removed from all transactions that use it. Destructive firefly_delete_transaction Permanently delete a transaction by its ID. This action cannot be undone.

WRITE 9 tools

Write firefly_create_account Create a new account in Firefly III. Account types: asset (bank accounts, wallets), expense (stores, services Write firefly_create_budget Create a new budget. Budgets help you track spending limits. Auto-budget options: - Write firefly_create_category Create a new transaction category. Write firefly_create_tag Create a new tag for labeling transactions. Write firefly_update_account Update an existing account. Only provide fields you want to change. Write firefly_update_budget Update an existing budget Write firefly_update_category Update an existing category Write firefly_update_tag Update an existing tag Write firefly_update_transaction Update an existing transaction. Only provide the fields you want to change. First use firefly_get_transaction

READ 8 tools

Read firefly_get_account Get a single account by ID with full details. Read firefly_get_transaction Get a single transaction by its ID. Returns full details including all splits. Read firefly_list_accounts List accounts with optional type filter. Returns account names, balances, and types. Read firefly_list_budgets List all budgets with their auto-budget configuration. Read firefly_list_categories List all categories. Use categories to classify transactions (e.g. Groceries, Rent, Entertainment). Read firefly_list_tags List all tags. Tags are flexible labels you can attach to transactions. Read firefly_list_transactions List transactions from Firefly III with optional filters. Supports filtering by type (withdrawal, deposit, tr Read firefly_search_transactions Search transactions using Firefly III

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Firefly III MCP Server

Can an AI agent move money through the Firefly III MCP Server MCP server? +

Yes. The Firefly III MCP Server server exposes 1 financial tools including firefly_create_transaction. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

Can an AI agent delete data through the Firefly III MCP Server MCP server? +

Yes. The Firefly III MCP Server server exposes 5 destructive tools including firefly_delete_account, firefly_delete_budget, firefly_delete_category. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Firefly III MCP Server? +

The Firefly III MCP Server server has 9 write tools including firefly_create_account, firefly_create_budget, firefly_create_category. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Firefly III MCP Server.

How many tools does the Firefly III MCP Server MCP server expose? +

23 tools across 3 categories: Destructive, Read, Write. 8 are read-only. 15 can modify, create, or delete data.

How do I enforce a policy on Firefly III MCP Server? +

Register the Firefly III MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Firefly III MCP Server tool call.

Deterministic rules across all 23 Firefly III MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON FIREFLY III →

Instant setup, no code required.

23 Firefly III MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.