firefly_delete_transaction

Permanently delete a transaction by its ID. This action cannot be undone.

Server Firefly III MCP Server przbadu/firefly-iii-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What firefly_delete_transaction does on Firefly III MCP Server

AI agents call firefly_delete_transaction to permanently remove resources in Firefly III MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why firefly_delete_transaction needs a policy

This tool irreversibly deletes financial transaction records, which is the definition of Destructive category. While it doesn't move money directly (which would be Financial), it destroys financial data that forms the audit trail and historical record of a user's finances. The consequence of misuse is high—an AI agent could delete important transaction records without recovery.

From the tool's definition Tool description explicitly states 'Permanently delete a transaction by its ID. This action cannot be undone.' The use of 'permanently delete' and 'cannot be undone' clearly indicates irreversible deletion of financial data.

Questions about firefly_delete_transaction

What does the firefly_delete_transaction tool do? +

Permanently delete a transaction by its ID. This action cannot be undone. It is categorised as a Destructive tool in the Firefly III MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on firefly_delete_transaction? +

Register the Firefly III MCP Server MCP server in PolicyLayer and add a rule for firefly_delete_transaction: 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.

What risk level is firefly_delete_transaction? +

firefly_delete_transaction is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit firefly_delete_transaction? +

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

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.