Search transactions using Firefly III
AI agents call firefly_search_transactions to retrieve information from Firefly III MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries transaction data without creating, modifying, deleting, or moving money. While Firefly III manages financial data, searching transactions is a passive information retrieval operation. The blast radius is minimal—misuse would only expose data visibility, not cause financial harm or data loss. Among sibling tools that include create/delete operations, this is clearly the least severe.
From the tool's definition Tool name contains 'search' and description states 'Search transactions using Firefly III' — a read-only query operation with no side effects.
Attacks that exploit this kind of access
Search transactions using Firefly III. It is categorised as a Read tool in the Firefly III MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Firefly III MCP Server MCP server in PolicyLayer and add a rule for firefly_search_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 Firefly III MCP Server. Nothing to install.
firefly_search_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 firefly_search_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 firefly_search_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.
firefly_search_transactions is provided by the Firefly III MCP Server MCP server (przbadu/firefly-iii-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →